From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: John Smith <horserivers@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: what is the function of EXCEPTIONS_SIGLONGJMP?
Date: Sat, 15 Sep 2012 06:08:00 -0000 [thread overview]
Message-ID: <20120915060824.GA19914@host2.jankratochvil.net> (raw)
In-Reply-To: <CAJR88pgQxHb7kjQ0MztcsrmQpt9qMLs+XZVayhV4oCUEwvo_tg@mail.gmail.com>
On Thu, 13 Sep 2012 11:55:34 +0200, John Smith wrote:
> when I debug gdb using gdb self , after I type "start" command ,
> the prompt is as below :
> Warning:
> Cannot insert breakpoint 0.
> Error accessing memory address 0xdb6a5194: /.
> 0xb7589571 in siglongjmp () from /lib/i686/cmov/libc.so.6
>
> it seem to be some exceptions happened when dealing with break points .
You are trying to step over longjmp or siglongjmp call. This is supported
only with SystemTap-extended glibc, this is implemented only in recent glibc
and recent GDB. Recent Fedora releases also have it working.
glibc/
commit 8422c9a560e6e3c854739c8a13ecb1c6714f930f
Author: Roland McGrath <roland@hack.frob.com>
Date: Fri May 25 13:31:57 2012 -0700
Add systemtap static probe points in setjmp/longjmp on x86.
gdb/
commit 014135139c612fe1fbe6f11d2350f72325a66f7c
Author: sergiodj <sergiodj>
Date: Fri Apr 27 20:48:52 2012 +0000
2012-04-27 Sergio Durigan Junior <sergiodj@redhat.com>
Tom Tromey <tromey@redhat.com>
I just do not understand how that can happen during 'start' command, 'start'
is just doing 'tbreak' and 'run', there is no stepping involved anywhere.
Regards,
Jan
next prev parent reply other threads:[~2012-09-15 6:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 9:55 John Smith
2012-09-15 6:08 ` Jan Kratochvil [this message]
2012-09-16 6:50 ` John Smith
2012-09-16 7:15 ` Jan Kratochvil
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=20120915060824.GA19914@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb@sourceware.org \
--cc=horserivers@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).