| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20081231083123.GF10725@disturbed> Date: Wed, 31 Dec 2008 19:31:23 +1100 From: Dave Chinner <david@...morbit.com> To: Daniel Phillips <phillips@...nq.net> Cc: tux3@...3.org, sniper <s3c24xx@...il.com>, linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org 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@...morbit.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists