From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Jie Zhang <jie.zhang@analog.com>, gdb-patches@sourceware.org
Subject: Re: PING: [PATCH] Fix a bug of addrmap
Date: Wed, 26 Nov 2008 13:53:00 -0000 [thread overview]
Message-ID: <m3d4gju1q9.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20081125174613.GF3946@adacore.com> (Joel Brobecker's message of "Tue\, 25 Nov 2008 09\:46\:13 -0800")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
Joel> Did you familiarize yourself with the code that you'd say that
Joel> the patch sounds good to you? If this is the case, I'm quite
Joel> happy to trust your judgement.
Not really, I'm afraid. I just wanted to make sure I understood the
bug report.
I still don't understand why the fix is to modify force_transition and
not addrmap_mutable_set_empty.
Joel> The one comment that I have about this is that it's not automatically
Joel> run when we run the testsuite. It would be really nice if they were.
Joel> It's not the first time that we have unit-testing like this.
Joel> For instance, check we have unit tests for observers, or xfullpath.
Joel> Traditionally, they have been implemented inside testsuite/gdb.gdb.
Joel> The current solution is not very elegant, in my opinion, as what we
Joel> did was debugging GDB and call some functions inside GDB.
Ugh. I definitely don't want to do that.
FWIW, in this case I was just following test-cp-name-parser.
Joel> How about, we add a testcase that "debugs" test-addrmap by simply
Joel> running it to completion and checking its output (including the
Joel> fact that it exited normally (meaning error code returned is zero)?
I will look into it.
Tom
next prev parent reply other threads:[~2008-11-25 17:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 4:44 Jie Zhang
2008-11-03 6:09 ` PING: " Jie Zhang
2008-11-25 23:09 ` Tom Tromey
2008-11-26 6:34 ` Joel Brobecker
2008-11-26 13:53 ` Tom Tromey [this message]
2008-11-26 14:24 ` Daniel Jacobowitz
2008-11-26 15:05 ` Daniel Jacobowitz
2008-11-27 14:45 ` Tom Tromey
2008-12-08 23:12 ` Joel Brobecker
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=m3d4gju1q9.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jie.zhang@analog.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