From: Stuart Hughes <stuarth@freescale.com>
To: xchen <xchen@sunrisetelecom.com.cn>
Cc: gdb@sourceware.org
Subject: Re: Unknown error with gdb [tcsetpgrp failed in terminal_inferior: Inappropriate ioctl for device]
Date: Thu, 23 Aug 2007 07:59:00 -0000 [thread overview]
Message-ID: <1187855851.3805.37.camel@m20> (raw)
In-Reply-To: <20070823025630.E5EB6D7FBF@cm-ms5.globat.com>
Hi Xi,
I'm not sure if it's the same isse, but in LTIB we have this patch for
gdb: http://www.bitshrine.org/gpp/gdb-6.3-tcsetpgrp-1.patch
Regards, Stuart
On Thu, 2007-08-23 at 10:55 +0800, xchen wrote:
> Hi
>
> I meet this error when I use gdb run on 860 board
>
> compile gdb
> CC=ppc_8xx-gcc AR=ppc_8xx-ar RANLIB=ppc_8xx-ranlib LD=ppc_8xx-ld ./configure
> --build=i686-linux --host=ppc-linux --prefix=/us
> r --sysconfdir=/etc |tee configure.out
> make 2>&1 | tee make.out
> make install 2>&1 | tee -a make.out
>
> belowed is the snapshot for gdb
>
> # cat hellogdb.c
> #include<stdio.h>
>
> int main()
> {
> int i=1;
> int m=2;
> printf("hello gdb\n");
> return 1;
> }
> # ./gdb hellogdb
> GNU gdb 6.6
> Copyright (C) 2006 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB. Type "show warranty" for details.
> This GDB was configured as "ppc-linux"...
> Using host libthread_db library "/lib/libthread_db.so.1".
> (gdb) b main
> Breakpoint 1 at 0x100003ec: file hellogdb.c, line 5.
> (gdb) run
> Starting program: /mnt/cf/system/hellogdb
> [tcsetpgrp failed in terminal_inferior: Inappropriate ioctl for device]
> [tcsetpgrp failed in terminal_inferior: Inappropriate ioctl for device]
> [tcsetpgrp failed in terminal_inferior: Inappropriate ioctl for device]
> [tcsetpgrp failed in terminal_inferior: Inappropriate ioctl for device]
>
> Breakpoint 1, main () at hellogdb.c:5
> 5 int i=1;
> (gdb) step
> [tcsetpgrp failed in terminal_inferior: Inappropriate ioctl for device]
> 6 int m=2;
>
> Does anyone know the reason?
>
> Thx
>
> Xi
>
next parent reply other threads:[~2007-08-23 7:59 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070823025630.E5EB6D7FBF@cm-ms5.globat.com>
2007-08-23 7:59 ` Stuart Hughes [this message]
2007-08-23 11:47 ` Daniel Jacobowitz
2007-08-23 2:56 xchen
-- strict thread matches above, loose matches on Subject: below --
2007-08-23 2:56 xchen
2007-08-23 2:56 xchen
2007-08-23 2:56 xchen
2007-08-23 2:56 xchen
2007-08-23 2:56 xchen
2007-08-23 2:56 xchen
2007-08-23 2:56 xchen
2007-08-23 2:56 xchen
2007-08-23 2:56 xchen
2007-08-23 2:56 xchen
2007-08-23 2:56 xchen
2007-08-23 2:56 xchen
2007-08-23 2:56 xchen
2007-08-23 2:56 xchen
2007-08-23 2:56 xchen
2007-08-23 2:56 xchen
2007-08-23 2:56 xchen
2007-08-23 2:56 xchen
2007-08-23 2:56 xchen
2007-08-23 2:56 xchen
2007-08-23 2:56 xchen
2007-08-23 2:56 xchen
2007-08-23 2:56 xchen
2007-08-23 2:56 xchen
1999-04-16 9:02 christophe leroy
1999-04-16 8:07 ` christophe leroy
1999-04-16 14:31 ` Philip Blundell
1999-04-26 9:48 ` christophe leroy
1999-04-26 8:26 ` christophe leroy
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=1187855851.3805.37.camel@m20 \
--to=stuarth@freescale.com \
--cc=gdb@sourceware.org \
--cc=xchen@sunrisetelecom.com.cn \
/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