> > Well, a test program that triggers the SIGABRT under gdb would be useful. The attached program causes a SIGABRT for me, Thanks, C.
#include <string> using namespace std; int main (char **argv, int argc) { string t = "linux rocks!"; t.replace(LONG_MAX, 1, "sigabrt here"); return 0; }
- 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]>
- 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: [PATCH] Dell laptop backlight driver
- Next by Date: Re: Syba 8-Port Serial Card Unidentified By Kernel
- 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):