On Sunday, 28 October 2007 16:33, C Sights wrote: > > > > Well, a test program that triggers the SIGABRT under gdb would be useful. > > The attached program causes a SIGABRT for me, > > Thanks, > C. Thanks, I'll try to reproduce the problem here and fix it. Greetings, Rafael - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- References:
- cannot "hibernate" if program being debugged in gdb is paused after SIGABRT in linux 2.6.23 (but can in 2.6.22.7)
- From: CSights <[email protected]>
- Re: cannot "hibernate" if program being debugged in gdb is paused after SIGABRT in linux 2.6.23 (but can in 2.6.22.7)
- From: "Rafael J. Wysocki" <[email protected]>
- Re: cannot "hibernate" if program being debugged in gdb is paused after SIGABRT in linux 2.6.23 (but can in 2.6.22.7)
- From: C Sights <[email protected]>
- cannot "hibernate" if program being debugged in gdb is paused after SIGABRT in linux 2.6.23 (but can in 2.6.22.7)
- Prev by Date: Re: WANTED: kernel projects for CS students
- Next by Date: RE: epoll design problems with common fork/exec patterns
- Previous by thread: Re: cannot "hibernate" if program being debugged in gdb is paused after SIGABRT in linux 2.6.23 (but can in 2.6.22.7)
- Next by thread: Re: cannot "hibernate" if program being debugged in gdb is paused after SIGABRT in linux 2.6.23 (but can in 2.6.22.7)
- Index(es):
 |