From: Daniel Berlin <dan@cgsoftware.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb@sources.redhat.com
Subject: Re: GDB on SGI Irix 6.5
Date: Mon, 09 Apr 2001 06:53:00 -0000 [thread overview]
Message-ID: <m2bsq6nprr.fsf@dynamic-addr-83-177.resnet.rochester.edu> (raw)
In-Reply-To: <Pine.SUN.3.91.1010409100338.27683O-100000@is>
Eli Zaretskii <eliz@is.elta.co.il> writes:
> Did someone successfully build the current CVS version on Irix 6.5? If
> so, are there any special tricks one need to be aware of to do that?
>
> I built GDB with "./configure; make" with the native C compiler and a
> native Make. While it built okay, the resulting binary aborts at runtime
> like this:
>
> (src)gdb ./emacs
> GNU gdb 20010402
> Copyright 2001 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 "mips-sgi-irix6.5"...
> Environment variable "DISPLAY" not defined.
> TERM = vt220
> Breakpoint 1 at 0x100ff7d0: file emacs.c, line 384.
> Breakpoint 2 at 0x100d8e18: file xterm.c, line 11714.
> (gdb) b main
> Breakpoint 3 at 0x100ffe48: file emacs.c, line 736.
> (gdb) r -q
> Starting program: /gnu/emacs-21/emacs-21.0.101/src/./emacs -q
> regcache.c:282: gdb-internal-error: Assertion `regnum >= 0 && regnum < (NUM_REGS + NUM_PSEUDO_REGS)' failed.
> An internal GDB error was detected. This may make further
> debugging unreliable. Continue this debugging session? (y or n)
>
> I've verified that this happens because legacy_read_register_gen is
> called with regnum = 72, while it doesn't expect any register to have a
> number greater than 71.
>
> Any clues?
This type of thing has been happening on IRIX for at least a year.
I remember getting a similar problem when I had an SGI machine for a
few months last year.
--
When I was little, my grandfather used to make me stand in a
closet for five minutes without moving. He said it was elevator
practice.
next prev parent reply other threads:[~2001-04-09 6:53 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-09 0:08 Eli Zaretskii
2001-04-09 6:53 ` Daniel Berlin [this message]
2001-04-17 10:38 ` Andrew Cagney
2001-04-18 9:29 ` Eli Zaretskii
2001-04-19 6:08 ` Eli Zaretskii
2001-04-30 10:01 ` Andrew Cagney
2001-04-30 11:28 ` Eli Zaretskii
2001-04-19 18:06 David B Anderson
2001-04-21 11:12 ` Eli Zaretskii
2001-04-21 12:09 ` Paul Hilfinger
2001-04-21 13:09 ` David B Anderson
2001-04-21 13:19 ` Eli Zaretskii
2001-05-17 8:58 ` Eli Zaretskii
2001-05-17 9:15 ` Eli Zaretskii
2001-05-17 9:26 ` Daniel Berlin
2001-05-17 9:28 ` Eli Zaretskii
2001-05-17 9:41 ` Daniel Berlin
2001-05-17 11:33 ` Eli Zaretskii
2001-05-17 11:47 ` Daniel Berlin
2001-05-17 10:15 David B Anderson
2001-05-17 11:40 ` Eli Zaretskii
2001-06-13 1:53 Eli Zaretskii
[not found] <200106131650.JAA27856@quasar.engr.sgi.com>
2001-06-13 11:40 ` Eli Zaretskii
2001-06-13 13:05 ` Andrew Cagney
[not found] <Pine.SUN.3.91.1010612152328.3699B-100000@is>
[not found] ` <3B266F35.50007@cygnus.com>
[not found] ` <15142.30117.72465.686304@kwikemart.cygnus.com>
2001-06-13 1:55 ` Eli Zaretskii
2001-06-13 13:35 ` David B Anderson
2001-06-13 21:19 ` Daniel Berlin
[not found] <npae3c16ia.fsf@zwingli.cygnus.com>
2001-06-14 0:52 ` Eli Zaretskii
2001-06-14 10:05 ` Daniel Berlin
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=m2bsq6nprr.fsf@dynamic-addr-83-177.resnet.rochester.edu \
--to=dan@cgsoftware.com \
--cc=eliz@is.elta.co.il \
--cc=gdb@sources.redhat.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