Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Min ZOU <zou.min@renesas.com>
To: gdb@sources.redhat.com
Subject: serial port conflicts
Date: Wed, 26 Jan 2005 09:18:00 -0000	[thread overview]
Message-ID: <41F7611C.9010009@renesas.com> (raw)

Hi,

I have implemented a gdb stub for a SH2 target based on "sh-stub.c" from 
GDB-v3.6 source. Now some basic features like step, break, cont, memory 
read/write, etc. are tested successfully.

The gdb stub and gdb on host communicate via remote serial protocol. 
However I have a problem to debug an application program, which accesses 
the same serial port used by gdb, e.g. I/O functions like "putstring()", 
"getchar()", etc. In my case, "putstring()" cannot display any message 
in gdb console, and "getchar()" cannot receive any input.

I guess there is a conflict between gdb and application program to 
access the same serial port. I'd like to hear any advice on solving this 
problem.

Thanks in advance!

-- 
Best Regards,
Min


             reply	other threads:[~2005-01-26  9:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-26  9:18 Min ZOU [this message]
2005-01-26 10:47 ` Ramana Radhakrishnan

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=41F7611C.9010009@renesas.com \
    --to=zou.min@renesas.com \
    --cc=gdb@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