From: Doug Evans <xdje42@gmail.com>
To: <lgustavo@codesourcery.com>
Cc: "'gdb-patches\@sourceware.org'" <gdb-patches@sourceware.org>,
Antoine Tremblay <antoine.tremblay@ericsson.com>
Subject: Re: [PATCH] Check for valid inferior before sending tracepoint packets
Date: Fri, 06 Feb 2015 07:57:00 -0000 [thread overview]
Message-ID: <m3r3u3jwwq.fsf@sspiff.org> (raw)
In-Reply-To: <54D42E15.5020108@codesourcery.com> (Luis Machado's message of "Fri, 6 Feb 2015 00:59:33 -0200")
Luis Machado <lgustavo@codesourcery.com> writes:
> This almost trivial patch prevents GDB from sending a few tracepoint
> packets when no inferior is selected. This robustifies things a bit
> and complements the fix Antoine submitted for gdbserver.
>
> I'm not quite sure how a testcase for this would look like given it
> needs extended-remote mode and also needs to connect to the target
> without a running inferior.
Hi.
The gdb.server/ext-run.exp testcase looks like it would be a
good starting point for such a testcase.
next prev parent reply other threads:[~2015-02-06 7:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 2:59 Luis Machado
2015-02-06 7:57 ` Doug Evans [this message]
2015-02-06 8:02 ` Doug Evans
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=m3r3u3jwwq.fsf@sspiff.org \
--to=xdje42@gmail.com \
--cc=antoine.tremblay@ericsson.com \
--cc=gdb-patches@sourceware.org \
--cc=lgustavo@codesourcery.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