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/31194] Stepping on "int3" instruction fails assertion.
Date: Sun, 31 Dec 2023 05:15:59 +0000 [thread overview]
Message-ID: <bug-31194-4717-UnOPhmEMt2@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31194-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31194
--- Comment #8 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom Tromey from comment #6)
> (In reply to Tom de Vries from comment #5)
>
> > I managed to reproduce, also on openSUSE Leap 15.4, not with system gcc 7,
> > but with gcc 8 and later.
>
> I wonder what's different for gcc 7.
> Perhaps the line table would be informative.
The difference is that for gcc 7, start stops at line 4 instead of 5, which I
failed to notice. With an extra step, I also manage to trigger the assertion
failure with gcc 7.
FWIW, line table gcc 7:
...
INDEX LINE REL-ADDRESS UNREL-ADDRESS IS-STMT PROLOGUE-END
0 4 0x0000000000400430 0x0000000000400430 Y
1 5 0x0000000000400431 0x0000000000400431 Y
2 6 0x0000000000400432 0x0000000000400432 Y
3 8 0x0000000000400434 0x0000000000400434 Y
4 6 0x000000000040043d 0x000000000040043d Y
5 8 0x0000000000400440 0x0000000000400440 Y
6 6 0x0000000000400445 0x0000000000400445 Y
7 10 0x000000000040044a 0x000000000040044a Y
8 END 0x000000000040044e 0x000000000040044e Y
...
and line table gcc 8:
...
INDEX LINE REL-ADDRESS UNREL-ADDRESS IS-STMT PROLOGUE-END
0 4 0x0000000000400430 0x0000000000400430 Y
1 5 0x0000000000400430 0x0000000000400430 Y
2 4 0x0000000000400430 0x0000000000400430
3 5 0x0000000000400431 0x0000000000400431
4 6 0x0000000000400432 0x0000000000400432 Y
5 6 0x0000000000400432 0x0000000000400432 Y
6 6 0x0000000000400432 0x0000000000400432
7 8 0x0000000000400434 0x0000000000400434 Y
8 6 0x000000000040043d 0x000000000040043d
9 8 0x0000000000400440 0x0000000000400440
10 6 0x0000000000400445 0x0000000000400445
11 10 0x000000000040044a 0x000000000040044a
12 10 0x000000000040044d 0x000000000040044d
13 END 0x000000000040044e 0x000000000040044e Y
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-12-31 5:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 22:54 [Bug gdb/31194] New: " peter0x44 at disroot dot org
2023-12-27 22:58 ` [Bug gdb/31194] " peter0x44 at disroot dot org
2023-12-27 23:04 ` peter0x44 at disroot dot org
2023-12-28 9:51 ` ssbssa at sourceware dot org
2023-12-28 11:25 ` vries at gcc dot gnu.org
2023-12-28 16:42 ` tromey at sourceware dot org
2023-12-29 5:57 ` vries at gcc dot gnu.org
2023-12-29 6:25 ` vries at gcc dot gnu.org
2023-12-29 18:25 ` tromey at sourceware dot org
2023-12-30 17:30 ` tromey at sourceware dot org
2023-12-31 1:46 ` peter0x44 at disroot dot org
2023-12-31 5:15 ` vries at gcc dot gnu.org [this message]
2023-12-31 20:02 ` tromey at sourceware dot org
2023-12-31 20:45 ` tromey at sourceware dot org
2024-01-07 22:03 ` peter0x44 at disroot dot org
2024-01-10 18:43 ` tromey at sourceware dot org
2024-02-08 19:10 ` tromey at sourceware dot 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-31194-4717-UnOPhmEMt2@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).