From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Ulrich Weigand <uweigand@de.ibm.com>, gdb-patches@sourceware.org
Subject: Re: [rfc v3][0/6] Remote /proc file access
Date: Wed, 18 Jan 2012 12:09:00 -0000 [thread overview]
Message-ID: <4F16B0F8.2020109@redhat.com> (raw)
In-Reply-To: <20120118113807.GA31383@adacore.com>
On 01/18/2012 11:38 AM, Joel Brobecker wrote:
> I ran the testsuite on mips-irix, and got one real semi-regression:
>
> info proc^M
> Not supported on this target.^M
> (gdb) FAIL: gdb.base/info-proc.exp: info proc without a process
>
> I think it's just a matter of the output having changed.
This looks like caused by the new target method not falling back to the
default run target when no target is pushed yet. "info proc PID" must have
stopped working too. I guess we should really make it fallback, while we
still have the method.
> I couldn't verify it completely, because I had lost the gdb.log file from the
> reference run (they are now split, and I only saved the top one).
> If it wasn't intended, I'd still consider this an improvement since
> the expected output was:
--
Pedro Alves
next prev parent reply other threads:[~2012-01-18 11:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 19:41 Ulrich Weigand
2012-01-17 20:19 ` Pedro Alves
2012-01-17 20:33 ` Ulrich Weigand
2012-01-18 11:46 ` Joel Brobecker
2012-01-18 12:09 ` Pedro Alves [this message]
2012-01-18 15:33 ` Ulrich Weigand
2012-01-19 10:00 ` Joel Brobecker
2012-01-19 10:01 ` [rfc v4][0/6] Remote /proc file access (Re: [rfc v3][0/6] Remote /proc file access) Ulrich Weigand
2012-01-19 16:03 ` Joel Brobecker
2012-01-20 10:01 ` Joel Brobecker
2012-01-20 10:02 ` Ulrich Weigand
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=4F16B0F8.2020109@redhat.com \
--to=palves@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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