From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: fix address in call to val_print
Date: Sun, 23 Nov 2008 21:15:00 -0000 [thread overview]
Message-ID: <m37i6vabyf.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20081122051123.GC4318@adacore.com> (Joel Brobecker's message of "Fri\, 21 Nov 2008 21\:11\:24 -0800")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
>> * valprint.c (val_print_array_elements): Pass correct
>> element address to val_print.
Joel> I'm wondering about the testcase. As I understand it, it wouldn't cause
Joel> any problem with the current FSF version of GDB. But if it's easy to
Joel> create one, then I think it'd still be a useful test to have, just to
Joel> make sure it doesn't regress in the future.
Ok, I will hold off on this patch until I can make a test case.
Tom
next prev parent reply other threads:[~2008-11-22 17:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 16:22 Tom Tromey
2008-11-22 18:16 ` Joel Brobecker
2008-11-23 21:15 ` Tom Tromey [this message]
2008-11-23 23:06 ` Joel Brobecker
2008-11-24 1:41 ` Tom Tromey
2008-11-24 2:30 ` Joel Brobecker
2008-11-24 3:09 ` Tom Tromey
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=m37i6vabyf.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@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