From: Daniel Jacobowitz <drow@mvista.com>
To: gdb@sources.redhat.com
Subject: Bizarre internal errors in regcache
Date: Mon, 26 Aug 2002 11:55:00 -0000 [thread overview]
Message-ID: <20020826185639.GA19722@nevyn.them.org> (raw)
I see this error on my laptop but not on my desktop; both current trees,
both rebuilt from scratch, both i386-linux. Any ideas?
info source
Current source file is ../../../src-gdb/gdb/testsuite/gdb.asm/asmsrc1.s
Located in /home/drow/src/gdb/src-gdb/gdb/testsuite/gdb.asm/asmsrc1.s
Contains 63 lines.
Source language is asm.
Compiled with stabs debugging format.
Does not include preprocessor macro info.
(gdb) PASS: gdb.asm/asm-source.exp: info source asmsrc1.s
finish
Run till exit from #0 foo3 () at ../../../src-gdb/gdb/testsuite/gdb.asm/asmsrc1.s:44
foo2 () at ../../../src-gdb/gdb/testsuite/gdb.asm/asmsrc2.s:13
13 gdbasm_call foo3
../../src-gdb/gdb/regcache.c:472: gdb-internal-error: set_register_cached: Assertion `regnum < current_regcache->descr->nr_raw_registers' failed.
An internal GDB error was detected. This may make further
debugging unreliable. Quit this debugging session? (y or n) ERROR: Got interactive prompt.
UNRESOLVED: gdb.asm/asm-source.exp: finish from foo3
n
info source
Create a core file containing the current state of GDB? (y or n) ERROR: Got interactive prompt.
UNRESOLVED: gdb.asm/asm-source.exp: info source asmsrc2.s
n
info sources
Please answer y or n.
Create a core file containing the current state of GDB? (y or n) (gdb) FAIL: gdb.asm/asm-source.exp: info sources
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next reply other threads:[~2002-08-26 18:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-26 11:55 Daniel Jacobowitz [this message]
2002-08-26 12:51 ` Daniel Jacobowitz
2002-08-26 13:28 ` Mark Kettenis
2002-08-26 13:54 ` Daniel Jacobowitz
2002-09-01 15:12 ` [PATCH] " Mark Kettenis
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=20020826185639.GA19722@nevyn.them.org \
--to=drow@mvista.com \
--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