Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: Caroline Tice <cmtice@google.com>,  Tom Tromey <tom@tromey.com>,
	 Eric Christopher <echristo@google.com>,
	 Simon Marchi <simark@simark.ca>,
	Caroline Tice via Gdb-patches <gdb-patches@sourceware.org>,
	 Joseph Myers <joseph@codesourcery.com>
Subject: Re: [PATCH] Update testsuite mechanism to allow object files as source files.
Date: Fri, 17 Jul 2020 11:45:28 -0600	[thread overview]
Message-ID: <87r1takpc7.fsf@tromey.com> (raw)
In-Reply-To: <20200717094358.GK2737@embecosm.com> (Andrew Burgess's message of "Fri, 17 Jul 2020 10:43:58 +0100")

>>>>> "Andrew" == Andrew Burgess <andrew.burgess@embecosm.com> writes:

Andrew> * Caroline Tice via Gdb-patches <gdb-patches@sourceware.org> [2020-07-16 14:10:25 -0700]:
>> Has the DWARF assembler in the GDB testsuite been updated to handle
>> DWARF v5?  Or can it handle that automatically?  Is there a good
>> example I can look at to see how to use it?

Andrew> To find examples look for the pattern 'Dwarf::assemble" in
Andrew> gdb/testsuite/gdb.dwarf2/*.exp.

There are also comments in gdb/testsuite/lib/dwarf.exp explaining how to
use it.

Tom


      reply	other threads:[~2020-07-17 17:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-16 16:50 Caroline Tice
2020-07-16 17:21 ` Andrew Burgess
2020-07-16 18:07   ` Caroline Tice
2020-07-16 18:29     ` Andrew Burgess
2020-07-16 17:33 ` Joseph Myers
2020-07-16 18:13   ` Caroline Tice
2020-07-16 18:47     ` Andrew Burgess
2020-07-16 20:35     ` Joseph Myers
2020-07-16 20:12   ` Tom Tromey
2020-07-16 21:10     ` Caroline Tice
2020-07-16 21:16       ` Eric Christopher
2020-07-17  9:48         ` Andrew Burgess
2020-07-17 16:05           ` Caroline Tice
2020-07-17  9:43       ` Andrew Burgess
2020-07-17 17:45         ` 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=87r1takpc7.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=andrew.burgess@embecosm.com \
    --cc=cmtice@google.com \
    --cc=echristo@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=joseph@codesourcery.com \
    --cc=simark@simark.ca \
    /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