From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: brobecker@gnat.com, cagney@gnu.org, gdb-patches@sources.redhat.com
Subject: Re: Problems with dejagnu and c++ tests...
Date: Wed, 04 Feb 2004 23:55:00 -0000 [thread overview]
Message-ID: <20040204235449.GA28988@nevyn.them.org> (raw)
In-Reply-To: <20040204235029.2F9374B364@berman.michael-chastain.com>
On Wed, Feb 04, 2004 at 06:50:29PM -0500, Michael Chastain wrote:
> drow> I think assuming we can compile and run is fine. Output is an
> drow> absolutely no-show, however. Take a look at how many of our supported
> drow> targets don't have any kind of remote file I/O capability - gdbserver,
> drow> for one.
>
> Argh. Okay. Although I'm not talking about file I/O, I'm talking
> about write to stdout. There are 58 *.[Cc] files with printf already.
Yes. They don't work on many remote setups, either :) Most of them
are guarded by gdb,noinferiorio.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-02-04 23:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 23:50 Michael Elizabeth Chastain
2004-02-04 23:55 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-04 23:03 Michael Elizabeth Chastain
2004-02-04 23:13 ` Daniel Jacobowitz
2004-02-04 22:31 Michael Elizabeth Chastain
2004-02-04 22:49 ` Andrew Cagney
2004-02-04 14:01 Michael Elizabeth Chastain
2004-02-04 15:41 ` Andrew Cagney
2004-02-04 12:50 Michael Elizabeth Chastain
2004-02-04 13:20 ` Joel Brobecker
2004-02-04 11:58 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=20040204235449.GA28988@nevyn.them.org \
--to=drow@mvista.com \
--cc=brobecker@gnat.com \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.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