From: Tom Tromey <tromey@redhat.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: jan.kratochvil@redhat.com, gdb-patches@sourceware.org
Subject: Re: [testsuite commit] Fix -m32 results [Re: [PATCH] Remove some KPASSes in gdb.base/callfuncs.exp]
Date: Wed, 24 Oct 2012 16:19:00 -0000 [thread overview]
Message-ID: <874nljalmw.fsf@fleche.redhat.com> (raw)
In-Reply-To: <201210241505.q9OF5fOg003231@glazunov.sibelius.xs4all.nl> (Mark Kettenis's message of "Wed, 24 Oct 2012 17:05:41 +0200 (CEST)")
>>>>> "Mark" == Mark Kettenis <mark.kettenis@xs4all.nl> writes:
Mark> Well gdb.log is what I actually look at when I'm trying to fix a bug.
Mark> Which I did, so the issue is gone from callfuncs.exp. Easier than
Mark> arguing about it.
If it is confusing, it would not be hard to add a note to the output
saying what proc is generating all the output.
Tom
prev parent reply other threads:[~2012-10-24 16:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 18:27 [PATCH] Remove some KPASSes in gdb.base/callfuncs.exp Mark Kettenis
2012-10-24 13:48 ` [testsuite commit] Fix -m32 results [Re: [PATCH] Remove some KPASSes in gdb.base/callfuncs.exp] Jan Kratochvil
2012-10-24 14:35 ` Mark Kettenis
2012-10-24 14:50 ` Jan Kratochvil
2012-10-24 15:05 ` Mark Kettenis
2012-10-24 16:19 ` 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=874nljalmw.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=mark.kettenis@xs4all.nl \
/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