At Thu, 15 Jan 2004 23:23:53 -0500, Daniel Jacobowitz wrote: > On Fri, Jan 16, 2004 at 01:22:10PM +0900, GOTO Masanori wrote: > > At Thu, 6 Nov 2003 13:14:04 -0500, > > Daniel Jacobowitz wrote: > > > > > > On Thu, Nov 06, 2003 at 05:39:23PM +0000, Andrew Suffield wrote: > > > > Package: libc6 > > > > Severity: important > > > > > > > > This may turn out to be a gdb bug, but let's start here... > > > > > > That just means GDB can't backtrace through abort. The compiler knows > > > that abort is a noreturn function, and is allowed to take all sorts of > > > liberties with the calling sequence - there's very little the debugger > > > can do. > > > > > > You won't be able to get a backtrace at least until GDB and your kernel > > > agree on how to dump the sysinfo DSO to a core dump and how to parse > > > it. The code's still being worked on. > > > > If so, how to handle this bug report? I think a core dump gotten > > throught abort() should also be enable to attach with gdb. Is this > > feature lack from gcc or gdb or nptl ? > > GDB and the kernel, IIRC. The most recent kernels probably do the > right thing. I need to recheck this and then I'll see about GDB > patches.
Thanks! So... should this bug reassign to gdb? Regards, -- gotom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
