From: "Jeff Millar" <jeff@wa1hco.mv.com>
To: "Graham Stoney" <greyham@research.canon.com.au>
Cc: "LinuxPPC Embedded Mailing List" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: gdb from mbxroot.full.tgz complains: Not a typewriter
Date: Wed, 16 Feb 2000 20:32:01 -0500 [thread overview]
Message-ID: <004701bf78e6$d2ab0de0$0201a8c0@home> (raw)
In-Reply-To: 20000217005917.4338F1B580@elph.research.canon.com.au
you need Dan Malek's sash patch. In addition, complicated terminal I/O might
be affected by a bug that Pavel Roskin fixed a few days ago (and posted
here).
jeff
----- Original Message -----
From: "Graham Stoney" <greyham@research.canon.com.au>
To: "LinuxPPC Embedded Mailing List" <linuxppc-embedded@lists.linuxppc.org>
Sent: Wednesday, February 16, 2000 7:59 PM
Subject: gdb from mbxroot.full.tgz complains: Not a typewriter
>
> I'm using mbxroot.full.tgz to develop/test a linuxppc-embedded application
on
> an Embedded Planet CLLF board, and I'm having some trouble running its gdb
> on the target. (I'm not using gdbserver here). When I run my program under
> gdb, and it stops at a breakpoint, I get the warning:
>
> [tcsetpgrp failed in terminal_inferior: Not a typewriter]
>
> after this, gdb no longer accepts my keyboard input.
>
> My guess is that the problem is caused by the kernel simply spawning a
shell
> without starting init, and is probably the same thing that stops CTRL-C
working
> on the console shell. My question then, is this: what's the simplest way
to
> make a shell on the console act like a normal shell on a host machine?
>
> Thanks,
> Graham
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-02-17 1:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-17 0:59 gdb from mbxroot.full.tgz complains: Not a typewriter Graham Stoney
2000-02-17 1:32 ` Jeff Millar [this message]
2000-02-17 15:46 ` Dan Malek
2000-02-19 9:51 ` How to build cross-compile environment under unix-similar cygwin on Win98 ? dony
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='004701bf78e6$d2ab0de0$0201a8c0@home' \
--to=jeff@wa1hco.mv.com \
--cc=greyham@research.canon.com.au \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).