Messages in this thread | | | From | "Rafael J. Wysocki" <> | Subject | 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) | Date | Sat, 27 Oct 2007 01:38:15 +0200 |
| |
On Friday, 26 October 2007 03:03, CSights wrote: > Hi LKML, > My computer running kernel 2.6.23 does not "hibernate" (suspend to disk using > the kernel's methods) with a program (named stringTest) running in gdb, but > has received a SIGABRT. > The hibernate is successful when running kernel 2.6.22.7 !
Certainly one of the freezer changes in 2.6.23 has caused that to happen ...
> Here is the message from gdb: > > terminate called after throwing an instance of 'std::out_of_range' > what(): basic_string::substr > > Program received signal SIGABRT, Aborted. > 0xb7fb6410 in __kernel_vsyscall () > > And the attached file is the portion of /var/log/syslog when the hibernate was > attempted. > > Let me know if there is anything else to send,
Well, a test program that triggers the SIGABRT under gdb would be useful.
Greetings, Rafael - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |