public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/14548] reverse: cannot step-over jmp-only-functions
Date: Mon, 17 Sep 2012 07:10:00 -0000	[thread overview]
Message-ID: <bug-14548-4717-Fb7w4r2eOx@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14548-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=14548

--- Comment #4 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> 2012-09-17 07:09:43 UTC ---
CVSROOT:    /cvs/src
Module name:    src
Changes by:    jkratoch@sourceware.org    2012-09-17 07:09:35

Modified files:
    gdb            : ChangeLog infrun.c 
    gdb/testsuite  : ChangeLog 
Added files:
    gdb/testsuite/gdb.reverse: singlejmp-reverse-nodebug.S 
                               singlejmp-reverse-nodebug.c 
                               singlejmp-reverse.S 
                               singlejmp-reverse.c 
                               singlejmp-reverse.exp 

Log message:
    gdb/
    PR 14548
    * infrun.c (handle_inferior_event): Do not reverse-continue back to the
    function start if we are already at function start.  Both for
    reverse-next and for reverse-step into function without line number
    info.

    gdb/testsuite/
    PR 14548
    * gdb.reverse/singlejmp-reverse-nodebug.S: New file.
    * gdb.reverse/singlejmp-reverse-nodebug.c: New file.
    * gdb.reverse/singlejmp-reverse.S: New file.
    * gdb.reverse/singlejmp-reverse.c: New file.
    * gdb.reverse/singlejmp-reverse.exp: New file.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/ChangeLog.diff?cvsroot=src&r1=1.14662&r2=1.14663
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/infrun.c.diff?cvsroot=src&r1=1.557&r2=1.558
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/testsuite/ChangeLog.diff?cvsroot=src&r1=1.3374&r2=1.3375
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/testsuite/gdb.reverse/singlejmp-reverse-nodebug.S.diff?cvsroot=src&r1=NONE&r2=1.1
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/testsuite/gdb.reverse/singlejmp-reverse-nodebug.c.diff?cvsroot=src&r1=NONE&r2=1.1
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/testsuite/gdb.reverse/singlejmp-reverse.S.diff?cvsroot=src&r1=NONE&r2=1.1
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/testsuite/gdb.reverse/singlejmp-reverse.c.diff?cvsroot=src&r1=NONE&r2=1.1
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/testsuite/gdb.reverse/singlejmp-reverse.exp.diff?cvsroot=src&r1=NONE&r2=1.1

-- 
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.


  parent reply	other threads:[~2012-09-17  7:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-06  9:00 [Bug gdb/14548] New: " jan.kratochvil at redhat dot com
2012-09-06  9:02 ` [Bug gdb/14548] " jan.kratochvil at redhat dot com
2012-09-06  9:04 ` jan.kratochvil at redhat dot com
2012-09-12 18:05 ` jan.kratochvil at redhat dot com
2012-09-17  7:10 ` cvs-commit at gcc dot gnu.org [this message]
2012-09-17  7:15 ` cvs-commit at gcc dot gnu.org
2012-09-17  7:22 ` jan.kratochvil at redhat dot com

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-14548-4717-Fb7w4r2eOx@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).