Re: [uml-devel] Re: handle_trap - failed to wait at end of syscall [was Re: [uml- devel] debugging UML cores]

[Jeff Dike <jdike@addtoit.com>]

dbahi@enterasys.com said:
> does this look familar? humm, here's 2.4.26-3um, backtrace attached. 

Not even close to the same bug.  It's segfaulting at neighbour.c, line 1341,
which is this:

  1340          ci.ndm_used = now - n->used;
  1341          ci.ndm_confirmed = now - n->confirmed;
  1342          ci.ndm_updated = now - n->updated;

This is mystifying because whatever address that line 1341 could have faulted 
on, line 1340 should have faulted.  The fault address is 61 (== 0x3d), which
I can't see in that code either.  If n were 0, then you'd get a fault on some
low address, but
	n = 0x260535a0 (and I assume you're using the new load-low option)
	n->confirmed is a 4-byte aligned field, and would not fault on an
odd address.

So, I think I don't totally trust gdb's line number reporting in this case.
What I would do is disassemble neigh_fill_info, and see what line the faulting
instruction really belongs to.

				Jeff



-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel