public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/9270] Stepping over longjmp presumably broken for glibc
Date: Sat, 15 Sep 2012 06:11:00 -0000 [thread overview]
Message-ID: <bug-9270-4717-yoCZlRbxvz@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-9270-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=9270
Jan Kratochvil <jan.kratochvil at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
CC| |jan.kratochvil at redhat
| |dot com
Resolution| |FIXED
AssignedTo|unassigned at sourceware |sergiodj at redhat dot com
|dot org |
--- Comment #2 from Jan Kratochvil <jan.kratochvil at redhat dot com> 2012-09-15 06:10:38 UTC ---
This is fixed now.
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>
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
prev parent reply other threads:[~2012-09-15 6:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-9270-4717@http.sourceware.org/bugzilla/>
2011-07-29 20:03 ` tromey at redhat dot com
2012-09-15 6:11 ` jan.kratochvil at redhat dot com [this message]
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=bug-9270-4717-yoCZlRbxvz@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.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 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).