From: christophe leroy <leroy@ensea.fr>
To: Philip Blundell <philb@gnu.org>
Cc: gdb@cygnus.com
Subject: Re: Unknown error with gdb [tcsetpgrp failed in terminal_inferior: Inappropriate ioctl for device]
Date: Mon, 26 Apr 1999 09:48:00 -0000 [thread overview]
Message-ID: <3724A1E2.70A9973C@ensea.fr> (raw)
In-Reply-To: <E10YGBG-0007Tj-00@kings-cross.london.uk.eu.org>
Philip Blundell wrote:
> >Does someone knows why I'm getting such an error when triing to run
> >something with gdb on an arm processor :
>
> Try gdb 4.18 with the patch I posted to this mailing list a few days ago. You
> need to be running a 2.2.5 kernel patched with the latest diff from my
> directory on ftp.netwinder.org for native breakpoints to work, though.
>
> p.
I've tried this and get the following problems.
- Patch, found on http://sourceware.cygnus.com , i've got some ununderstandable
rejects. Applied by hand
- Configure in readline directory doesn't like cross compiling.
What can I do ?
christophe
WARNING: multiple messages have this Message-ID
From: christophe leroy <leroy@ensea.fr>
To: Philip Blundell <philb@gnu.org>
Cc: gdb@cygnus.com
Subject: Re: Unknown error with gdb [tcsetpgrp failed in terminal_inferior: Inappropriate ioctl for device]
Date: Mon, 26 Apr 1999 08:26:00 -0000 [thread overview]
Message-ID: <3724A1E2.70A9973C@ensea.fr> (raw)
Message-ID: <19990426082600.kE4H6X_-kBX_udzpr4jvHHxVvplqn9szURJLujL1Kvs@z> (raw)
In-Reply-To: <E10YGBG-0007Tj-00@kings-cross.london.uk.eu.org>
Philip Blundell wrote:
> >Does someone knows why I'm getting such an error when triing to run
> >something with gdb on an arm processor :
>
> Try gdb 4.18 with the patch I posted to this mailing list a few days ago. You
> need to be running a 2.2.5 kernel patched with the latest diff from my
> directory on ftp.netwinder.org for native breakpoints to work, though.
>
> p.
I've tried this and get the following problems.
- Patch, found on http://sourceware.cygnus.com , i've got some ununderstandable
rejects. Applied by hand
- Configure in readline directory doesn't like cross compiling.
What can I do ?
christophe
next prev parent reply other threads:[~1999-04-26 9:48 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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=3724A1E2.70A9973C@ensea.fr \
--to=leroy@ensea.fr \
--cc=gdb@cygnus.com \
--cc=philb@gnu.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