From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19650 invoked by alias); 20 Jun 2006 12:27:16 -0000 Received: (qmail 19640 invoked by uid 22791); 20 Jun 2006 12:27:15 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Tue, 20 Jun 2006 12:27:14 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1FsfJz-0005Hw-Mm; Tue, 20 Jun 2006 08:27:07 -0400 Date: Tue, 20 Jun 2006 12:28:00 -0000 From: Daniel Jacobowitz To: Fahd Abidi Cc: gdb@sourceware.org Subject: Re: Trying to remote debug question Message-ID: <20060620122707.GD20079@nevyn.them.org> Mail-Followup-To: Fahd Abidi , gdb@sourceware.org References: <81C69D96BDD30640952C7A404004AA2543A7A3@ultsol01.tewks.ultsol.local> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <81C69D96BDD30640952C7A404004AA2543A7A3@ultsol01.tewks.ultsol.local> User-Agent: Mutt/1.5.11+cvs20060403 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-06/txt/msg00134.txt.bz2 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