From: Simon Marchi <simark@simark.ca>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/5] Change linetables to be objfile-independent
Date: Sun, 12 Mar 2023 09:40:57 -0400 [thread overview]
Message-ID: <c3d99cf3-930c-cdbb-97f9-557c8711540d@simark.ca> (raw)
In-Reply-To: <87fsaaejnb.fsf@tromey.com>
On 3/11/23 22:24, Tom Tromey wrote:
> Simon> FAIL: gdb.base/async.exp: stepi&
> Simon> FAIL: gdb.base/async.exp: nexti&
> Simon> FAIL: gdb.base/async.exp: finish&
> Simon> FAIL: gdb.base/consecutive.exp: stopped at bp, 2nd instr (missing hex prefix)
> Simon> FAIL: gdb.base/disasm-optim.exp: Disassemble main with source (pattern 2)
> Simon> FAIL: gdb.dwarf2/dw2-disasm-over-non-stmt.exp: opt=s: disassemble /s main
> Simon> FAIL: gdb.dwarf2/dw2-disasm-over-non-stmt.exp: opt=s: check_disassembly_results 16 line_label_1 (no disassembly for 16)
> Simon> FAIL: gdb.dwarf2/dw2-disasm-over-non-stmt.exp: opt=s: check_disassembly_results 16 line_label_2 (no disassembly for 16)
> Simon> FAIL: gdb.dwarf2/dw2-disasm-over-non-stmt.exp: opt=s: check_disassembly_results 17 line_label_3 (no disassembly for 17)
> Simon> FAIL: gdb.dwarf2/dw2-disasm-over-non-stmt.exp: opt=s: check_disassembly_results 17 line_label_4 (no disassembly for 17)
> Simon> FAIL: gdb.dwarf2/dw2-disasm-over-non-stmt.exp: opt=s: check_disassembly_results 17 line_label_5 (no disassembly for 17)
> Simon> FAIL: gdb.dwarf2/dw2-disasm-over-non-stmt.exp: opt=s: check_disassembly_results 18 line_label_6 (no disassembly for 18)
> Simon> FAIL: gdb.reverse/consecutive-precsave.exp: stopped at bp, 2nd instr (missing hex prefix)
> Simon> FAIL: gdb.reverse/consecutive-reverse.exp: stopped at bp, 2nd instr (missing hex prefix)
>
> I tried these with git master and they all work fine for me. I wonder
> what the difference could be. Could you run one of them perhaps & send
> me the gdb.log? Maybe that would give a clue.
This for instance:
68 disassemble /s main^M
69 Dump of assembler code for function main:^M
70 gdb_expect_list pattern: /disasm-optim\.c:^M
71 24/
72 Cannot access memory at address 0x1130^M
73 (gdb) FAIL: gdb.base/disasm-optim.exp: Disassemble main with source (pattern 2)
Looks like we're trying to read from the inferior at an unrelocated
address. From some previous bug, I recall that you were using a system
with no-PIE as a default, so that could be why you don't see it.
Simon
next prev parent reply other threads:[~2023-03-12 13:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 15:42 [PATCH 0/5] Make line tables independent of objfile Tom Tromey
2023-03-08 15:42 ` [PATCH 1/5] Add operator< and operator== to linetable_entry Tom Tromey
2023-03-11 3:21 ` Simon Marchi
2023-03-08 15:42 ` [PATCH 2/5] Change linetables to be objfile-independent Tom Tromey
2023-03-11 3:48 ` Simon Marchi
2023-03-11 15:36 ` Tom Tromey
2023-03-11 19:13 ` Simon Marchi
2023-03-12 3:24 ` Tom Tromey
2023-03-12 13:40 ` Simon Marchi [this message]
2023-03-16 14:02 ` Tom Tromey
2023-03-16 14:45 ` Simon Marchi
2023-03-16 23:43 ` Tom Tromey
2023-03-17 2:45 ` Simon Marchi
2023-03-17 13:09 ` Tom Tromey
2023-03-17 22:21 ` Tom Tromey
2023-03-20 14:57 ` Simon Marchi
2023-03-08 15:42 ` [PATCH 3/5] Constify linetables Tom Tromey
2023-03-08 15:42 ` [PATCH 4/5] Remove extra scopes from objfile_relocate1 Tom Tromey
2023-03-08 15:42 ` [PATCH 5/5] Change linetable_entry::is_stmt to bool Tom Tromey
2023-03-11 3:51 ` [PATCH 0/5] Make line tables independent of objfile Simon Marchi
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=c3d99cf3-930c-cdbb-97f9-557c8711540d@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/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).