Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Fahd Abidi" <fabidi@ultsol.com>
To: "Daniel Jacobowitz" <drow@false.org>
Cc: <gdb@sourceware.org>
Subject: RE: Trying to remote debug question
Date: Tue, 20 Jun 2006 13:24:00 -0000	[thread overview]
Message-ID: <81C69D96BDD30640952C7A404004AA2543A7A8@ultsol01.tewks.ultsol.local> (raw)

Thank you, that sounds promising.

Would you happen to know the command to tell gdbserver to write its
stdout/stderr to /dev/null?

Fahd
 


-----Original Message-----
From: Daniel Jacobowitz [mailto:drow@false.org] 
Sent: Tuesday, June 20, 2006 8:31 AM
To: Fahd Abidi
Cc: gdb@sourceware.org
Subject: Re: Trying to remote debug question


On Mon, Jun 19, 2006 at 01:28:28PM -0400, Fahd Abidi wrote:
> Hello,
> 
> I am trying to launch a remote debug into my target, I have a mips 
> based board but with only one serial port and No ethernet. I use the 
> serial port as the target console for my 2.6 kernel.
> 
> I am wondering if I can launch the GDBServer to use /dev/ttyS0 even 
> though my Linux console is also tied to this com port? It is the only 
> comport available on the target so I have to try and use it for both 
> my console and remote debugging. When I try to launch a GDB session to

> this port it says "inappropriate IOCTL for this device".

There used to be a multiplexer, called kdmx, that allowed you to use one
port for both console and debug.  But I haven't seen a copy of it in a
few years now.

The inappropriate ioctl message can probably be ignored.  If you tell
gdbserver to write its stdout/stderr to /dev/null and to open a
connection to /dev/ttyS0, it should work.

-- 
Daniel Jacobowitz
CodeSourcery




             reply	other threads:[~2006-06-20 13:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-20 13:24 Fahd Abidi [this message]
2006-06-20 13:42 ` Daniel Jacobowitz
  -- strict thread matches above, loose matches on Subject: below --
2006-06-19 19:22 Fahd Abidi
2006-06-20 12:28 ` Daniel Jacobowitz

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=81C69D96BDD30640952C7A404004AA2543A7A8@ultsol01.tewks.ultsol.local \
    --to=fabidi@ultsol.com \
    --cc=drow@false.org \
    --cc=gdb@sourceware.org \
    /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