From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Stan Shebs <stan@codesourcery.com>
Subject: Re: [commit/RFC] fix gdb.trace/collection.exp bitrot
Date: Sun, 28 Mar 2010 23:47:00 -0000 [thread overview]
Message-ID: <201003290047.40489.pedro@codesourcery.com> (raw)
In-Reply-To: <201003290045.17238.pedro@codesourcery.com>
On Monday 29 March 2010 00:45:17, Pedro Alves wrote:
> I was adding a small test to gdb/trace/collection.exp for some
I meant, gdb.trace/collection.exp.
> other random tracing bug fix, and noticed that it actually
> never ran against gdbserver with tracepoints support. The
> test assumes that after gdb_load, which isn't true for all
... test assumes that after gdb_load, GDB is already connected
to a running target, ... which isn't true ...
> board files, or native testing. It's also not true with
> the local gdbserver testing boardfile found in the wiki,
> that most people use. The test was then always being
> skipped with that common pattern in gdb.trace/ tests:
--
Pedro Alves
next prev parent reply other threads:[~2010-03-28 23:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-28 23:45 Pedro Alves
2010-03-28 23:47 ` Pedro Alves [this message]
2010-03-31 21:31 ` Stan Shebs
2010-04-01 1:32 ` Pedro Alves
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=201003290047.40489.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=stan@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