Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: christophe leroy <leroy@ensea.fr>
To: gdb@cygnus.com
Subject: Unknown error with gdb [tcsetpgrp failed in terminal_inferior: Inappropriate ioctl for device]
Date: Fri, 16 Apr 1999 08:07:00 -0000	[thread overview]
Message-ID: <37176E57.48332685@ensea.fr> (raw)
Message-ID: <19990416080700.KmpiQVpgKIRkHx7SQk_jCWVS8qa04S6MIwT7kr3MDI4@z> (raw)

Does someone knows why I'm getting such an error when triing to run
something with gdb  on an arm processor :
BFD: /mnt/./tick: version count (4) does not match symbol count (8)

(gdb) run
Starting program: /mnt/./tick
[tcsetpgrp failed in terminal_inferior: Inappropriate ioctl for device]
BFD: /lib/libc.so.6: version count (847) does not match symbol count
(1695)
Cannot access memory at address 0x0.

I've managed to make the BFD related problem disappear by replacing bfd
subtree by binutils one.
the "tcsetpgrp failed" stays anyway
So if someone can help

Thanks

christophe

christophe leroy wrote:

> christophe leroy wrote:
>
> > Philip Blundell wrote:
> >
> >
> > I think i've found something.
> >
> >
http://master.debian.org/~davidw/netwinder/gdb_4.17-4.arm.m68k.objc.threads.hwwp.fpu.gnat.1.diff.gz

> >
> > christophe
> >
> > unsubscribe: body of `unsubscribe linux-arm' to
majordomo@vger.rutgers.edu
>
> I've compiled and tried gdb.  I've got errors !
>
> christophe
>
> init-2.02# bin/gdb ./tick
> GNU gdb 4.17.m68k.objc.threads.hwwp.fpu.gnat
> Copyright 1998 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 "arm-linux"...BFD: /mnt/./tick: version
count (4) does not match symbol
> count (8)
>
> (gdb) break main
> Breakpoint 1 at 0x20003d0: file tick.c, line 4.
> (gdb) run
> Starting program: /mnt/./tick
> [tcsetpgrp failed in terminal_inferior: Inappropriate ioctl for
device]
> BFD: /lib/libc.so.6: version count (847) does not match symbol count
(1695)
> Cannot access memory at address 0x0.
> (gdb)
>





             reply	other threads:[~1999-04-16  8:07 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-16  9:02 christophe leroy [this message]
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
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
2007-08-23  2:56 xchen
     [not found] <20070823025630.E5EB6D7FBF@cm-ms5.globat.com>
2007-08-23  7:59 ` Stuart Hughes
2007-08-23 11:47   ` 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=37176E57.48332685@ensea.fr \
    --to=leroy@ensea.fr \
    --cc=gdb@cygnus.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