From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Paul Pluzhnikov <ppluzhnikov@google.com>,
gdb-patches ml <gdb-patches@sourceware.org>,
Doug Evans <dje@google.com>
Subject: Re: [patch] Re: Advice on fixing gdb/12528
Date: Tue, 15 Mar 2011 15:45:00 -0000 [thread overview]
Message-ID: <20110315154323.GA19189@host1.jankratochvil.net> (raw)
In-Reply-To: <m34o749zbi.fsf@fleche.redhat.com>
On Tue, 15 Mar 2011 16:29:53 +0100, Tom Tromey wrote:
> >>>>> "Paul" == Paul Pluzhnikov <ppluzhnikov@google.com> writes:
> Jan> For a real testcase it should be in gdb.dwarf2/ (and then the special
> Jan> compilation options are sure no longer needed).
>
> Paul> Sorry, I didn't follow that part. Why special options wouldn't be needed?
>
> What Jan means is that you can put a .S file into gdb.dwarf2.
> That way the test is independent of compiler version (but unfortunately
> then dependent on arch).
Or coded like
gdb.dwarf2/dw2-ref-missing-frame*
with native code while still being arch-independent or the more simple case
gdb.dwarf2/dw2-filename*
where no native code was needed (and it is also arch-independent).
But in both cases it is a pain to code it by hand.
Regards,
Jan
next prev parent reply other threads:[~2011-03-15 15:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 17:09 Paul Pluzhnikov
2011-03-11 18:27 ` Tom Tromey
2011-03-14 21:16 ` [patch] " Paul Pluzhnikov
2011-03-15 3:16 ` Jan Kratochvil
2011-03-15 5:26 ` Paul Pluzhnikov
2011-03-15 15:35 ` Tom Tromey
2011-03-15 15:45 ` Jan Kratochvil [this message]
2011-03-15 16:00 ` Paul Pluzhnikov
2011-03-15 18:50 ` Jan Kratochvil
2011-03-15 19:12 ` Paul Pluzhnikov
2011-03-15 19:18 ` Jan Kratochvil
2011-03-15 19:41 ` Paul Pluzhnikov
2011-03-15 23:26 ` Jan Kratochvil
2011-03-16 0:13 ` Paul Pluzhnikov
2011-03-16 8:20 ` Jan Kratochvil
2011-03-16 17:43 ` Paul Pluzhnikov
2011-03-16 17:52 ` Jan Kratochvil
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=20110315154323.GA19189@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=ppluzhnikov@google.com \
--cc=tromey@redhat.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