Messages in this thread | | | Date | Wed, 31 Dec 2008 19:31:23 +1100 | From | Dave Chinner <> | Subject | Re: [Tux3] Tux3 report: A Golden Copy |
| |
On Wed, Dec 31, 2008 at 12:00:54AM -0800, Daniel Phillips wrote: > On Tuesday 30 December 2008 23:34, sniper wrote: > > Great, I have mounted tux3 filesystem under UML with stuffs in this mail, > > but I still can't debug it with gdb. Anyone gives me suggestion? .... > In the mean time, you could just tell gdb to mask off all segfaults, > but would be kind of problematic for debugging.
Not really. That's the default setting I use for XFS debugging. I just put breakpoints on "panic" and "stop" (sometimes bust_spinlocks) and just let the kernel panic routine handle the segv which will trip a breakpoint. Then just walk back up the stack to the function that triggered the real SEGV and go from there.
This is pretty much necessary for XFS debugging because just mounting a filesystem causes 8-10 SEGV signals to occur. You simply can't run xfsqa when that is occurring...
Cheers,
Dave. -- Dave Chinner david@fromorbit.com
| |