From: Tom Tromey <tom@tromey.com>
To: "Mock, George via Gdb" <gdb@sourceware.org>
Cc: "Mock, George" <gmock@ti.com>
Subject: Re: test gdb as it runs qemu simulator
Date: Fri, 31 Oct 2025 14:33:57 -0600 [thread overview]
Message-ID: <874irebykq.fsf@tromey.com> (raw)
In-Reply-To: <938d2b5574b94d9584b758eee3c0c064@ti.com> (George via Gdb Mock's message of "Wed, 29 Oct 2025 20:21:13 +0000")
>>>>> Mock, George via Gdb <gdb@sourceware.org> writes:
> I want to use the gdb testsuite. Not for the purpose
> of testing gdb, but to test whether the Dwarf generated by our
> compiler works with gdb.
FWIW it's not unusual to discover that valid DWARF can trigger a gdb
bug. Feel free to file bugs for that kind of thing. Or send patches.
thanks,
Tom
prev parent reply other threads:[~2025-10-31 20:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 20:21 Mock, George via Gdb
2025-10-29 22:05 ` Luis via Gdb
2025-10-31 20:32 ` Tom Tromey
2025-10-31 20:33 ` Tom Tromey [this message]
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=874irebykq.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb@sourceware.org \
--cc=gmock@ti.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