Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jun Sun <jsun@mvista.com>
To: linux-mips@fnet.fr, linux@cthulhu.engr.sgi.com
Cc: jpuhlman@mvista.com
Subject: Bus error of gdb 5.0 with MIPS patch
Date: Sat, 29 Jul 2000 09:05:57 -0700	[thread overview]
Message-ID: <398300E5.143F5370@mvista.com> (raw)


Hi,

I started to play with gdb 5.0 + the MIPS patch at
http://www.ds2.pg.gda.pl/~macro/gdb-5.0/, but I am having a bus error if
I want to do 'next step'.  Setting breakpoints and continuing running
seem to be fine.

The gdb 4.17 rpm from oss.sgi.com does not have this problem.

Any idea?

Jun

---------------

sh-2.03# ./gdb hello
GNU gdb 5.0 (UI_OUT)
Copyright 2000 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 "mipsel-hardhat-linux"...
(gdb) n
The program is not being run.
(gdb) b main
Breakpoint 1 at 0x400c24: file hello.c, line 5.
(gdb) r
Starting program: /tmp/hello 
[tcsetpgrp failed in terminal_inferior: Not a typewriter]
[tcsetpgrp failed in terminal_inferior: Not a typewriter]
[tcsetpgrp failed in terminal_inferior: Not a typewriter]

Breakpoint 1, main () at hello.c:5
5         printf("hello, world\n");
(gdb) n
[tcsetpgrp failed in terminal_inferior: Not a typewriter]
Bus error

-----------

P.S., Does anybody know how to fix "tcsetpgrp ..." error?

             reply	other threads:[~2000-07-29 16:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-29 16:05 Jun Sun [this message]
2000-07-30 11:29 ` Bus error of gdb 5.0 with MIPS patch Ralf Baechle
2000-07-31 16:22 ` Maciej W. Rozycki
2000-07-31 17:17   ` Jun Sun
2000-07-31 17:42     ` Maciej W. Rozycki

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=398300E5.143F5370@mvista.com \
    --to=jsun@mvista.com \
    --cc=jpuhlman@mvista.com \
    --cc=linux-mips@fnet.fr \
    --cc=linux@cthulhu.engr.sgi.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