public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/29196] [gdb, gcc-12/m32/pie] FAIL: gdb.base/gdb11531.exp: watchpoint variable triggers at next
Date: Sat, 28 May 2022 08:26:04 +0000	[thread overview]
Message-ID: <bug-29196-4717-nXfwZRD08l@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29196-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29196

--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
Hmm, but with -m64, both with and without -pie, we also have different
addresses for lines 33 and 34:
...
INDEX  LINE   ADDRESS            IS-STMT PROLOGUE-END 
0      33     0x0000000000401116 Y                    
1      34     0x000000000040111a Y                    
2      35     0x0000000000401124 Y                    
3      36     0x0000000000401134 Y                    
4      37     0x000000000040113e Y                    
5      38     0x0000000000401148 Y                    
6      39     0x000000000040114e Y                    
7      END    0x0000000000401150 Y                    
...
and we don't see the fail here, so maybe we can learn something from comparing
against this scenario as well.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-05-28  8:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-28  7:55 [Bug gdb/29196] New: " vries at gcc dot gnu.org
2022-05-28  8:04 ` [Bug gdb/29196] " vries at gcc dot gnu.org
2022-05-28  8:08 ` vries at gcc dot gnu.org
2022-05-28  8:26 ` vries at gcc dot gnu.org [this message]
2022-06-04 11:59 ` vries at gcc dot gnu.org
2022-06-08  9:17 ` vries at gcc dot gnu.org
2022-06-08  9:48 ` vries at gcc dot gnu.org

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