This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Trying to remote debug question


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




Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]