From: Keith Seitz <keiths@redhat.com>
To: Charles-Henri Balet <charles-henri@bluewin.ch>
Cc: <insight@sources.redhat.com>
Subject: Re: GDB error for angel on ARM oki board
Date: Sat, 23 Feb 2002 14:22:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.33.0202231417590.16592-100000@makita.cygnus.com> (raw)
In-Reply-To: <001101c1eb07$ed01ef70$0401a8c0@CHARLESHENRI>
See my previous response on this thread. We need to ascertain whether this
is a backend problem or a gui problem.
Once we know that, we should be able to find out what is wrong.
On Tue, 23 Apr 2002, Charles-Henri Balet wrote:
> I have compiled the GDB 5.1.1 and place the command : "target rdi com1", no
> effect, when I press the
> reset switch on the oki board an error message appear : "Unexpected read on
> channel 4, length 192"
Are you setting the baudrate? (set remotebaud XXXX) If you are using
either the command line or the console window to attach, you MUST set this
before attempting to attach.
> this message appear on each press on the reset switch, any has an idea ?
Doesn't ring any bells.
> Another question, how can I find the "DEBUG" define in the GDB source code
> for see more message on
> the run of this arm-elf-gdb, I have see on the source code of the rdi
> process that if DEBUG is defined, few
> message appear for follow the problem, can you give me the source file where
> this DEBUG is defined !
Probably add "-DDEBUG" to CFLAGS in rdi-share directory?
Keith
next prev parent reply other threads:[~2002-02-23 22:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-23 13:48 Charles-Henri Balet
2002-02-23 14:22 ` Keith Seitz [this message]
2002-04-04 10:51 ` Insight for X11 under Windoze Kai Ruottu
[not found] <001001c1eb76$4f96b670$0401a8c0@CHARLESHENRI>
2002-02-24 8:55 ` GDB error for angel on ARM oki board Keith Seitz
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=Pine.GSO.4.33.0202231417590.16592-100000@makita.cygnus.com \
--to=keiths@redhat.com \
--cc=charles-henri@bluewin.ch \
--cc=insight@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).