From: Grant Edwards <grante@visi.com>
To: Igor Trevisan <igor@bluewind.it>
Cc: gdb@sourceware.cygnus.com
Subject: Re: Angel and Insight
Date: Wed, 21 Mar 2001 15:59:00 -0000 [thread overview]
Message-ID: <20010305081400.A3663@visi.com> (raw)
In-Reply-To: <20010305080518.A3570@visi.com>
On Mon, Mar 05, 2001 at 08:05:18AM -0600, Grant Edwards wrote:
>
> > I forward you the message I received from "Insight" support
> > regarding a problem I have with gdb and Angel (ARM monitor). I
> > also attach the log file I obtained running my simple test
> > program (it's just something similar to the typical "Hello
> > World!") hoping this can help you to solve my problem.
>
> It looks like the following lines show the data from the
> printf()s being sent to gdb:
>
> R=80000069 H<-T CI_CLIB: CL_Write 40608010 0000000d 0000000d 61202932 2c30313d 333d6220 ffffff0a
> R=80000069 H<-T CI_CLIB: CL_Write 40608010 00000001 00000001 6120290a
> R=80000069 H<-T CI_CLIB: CL_Write 40608010 0000000d 0000000d 61202931 2c30313d 333d6220 0000000a
> R=80000069 H<-T CI_CLIB: CL_Write 40608010 00000001 00000001 6120290a
>
> It looks like the rdi target code isn't passing "stdout" data
> up to the next layer up...
The rdi code (hsys.c line 490 or so) doesn't pass data up to
gdb, it actually writes it to the requested file descriptor.
Are you sure that the message you wrote with printf() isn't
getting written to stdout? It looks like it should have been.
Have you tried running the program using "gdb -nw"?
--
Grant Edwards
grante@visi.com
prev parent reply other threads:[~2001-03-21 15:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-21 15:59 Igor Trevisan
2001-03-21 15:59 ` Grant Edwards
2001-03-21 15:59 ` Fernando Nasser
2001-03-21 15:59 ` Grant Edwards [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=20010305081400.A3663@visi.com \
--to=grante@visi.com \
--cc=gdb@sourceware.cygnus.com \
--cc=igor@bluewind.it \
/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