public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "philippe.waroquiers at skynet dot be" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/15156] New: breakpoint on labels in asm statement placed at wrong address
Date: Mon, 18 Feb 2013 22:01:00 -0000	[thread overview]
Message-ID: <bug-15156-4717@http.sourceware.org/bugzilla/> (raw)

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

             Bug #: 15156
           Summary: breakpoint on labels in asm statement placed at wrong
                    address
           Product: gdb
           Version: 7.5
            Status: NEW
          Severity: minor
          Priority: P2
         Component: breakpoints
        AssignedTo: unassigned@sourceware.org
        ReportedBy: philippe.waroquiers@skynet.be
    Classification: Unclassified


Created attachment 6875
  --> http://sourceware.org/bugzilla/attachment.cgi?id=6875
test program with a asm block with a label

Tested on Debian 6.0, gcc version 4.4.5 (Debian 4.4.5-8), x86_64-linux-gnu,
gdb 7.5

Compile the attached program with:
gcc -g -o self_invalidate self_invalidate.c

then do:
gdb ./self_invalidate
break top
break *top

The first command puts a breakpoint at another address than the 2nd command.
It is unclear either why the first command is accepted or else
why it puts a breakpoint at another address than the label top.


(gdb) break top
Breakpoint 1 at 0x400499: file self_invalidate.c, line 4.
(gdb) break *top
Breakpoint 2 at 0x40049e: file self_invalidate.c, line 4.
(gdb)

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


                 reply	other threads:[~2013-02-18 22:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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