From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: CSights <csights@fastmail.fm>
Cc: linux-kernel@vger.kernel.org
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 [thread overview]
Message-ID: <200710270138.15982.rjw@sisk.pl> (raw)
In-Reply-To: <200710252103.27675.csights@fastmail.fm>
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
next prev parent reply other threads:[~2007-10-26 23:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 1:03 cannot "hibernate" if program being debugged in gdb is paused after SIGABRT in linux 2.6.23 (but can in 2.6.22.7) CSights
2007-10-26 23:38 ` Rafael J. Wysocki [this message]
2007-10-28 15:33 ` C Sights
2007-10-28 18:58 ` Rafael J. Wysocki
2007-10-30 14:34 ` CSights
2007-11-08 22:50 ` Rafael J. Wysocki
2007-11-09 13:30 ` CSights
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200710270138.15982.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=csights@fastmail.fm \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.