public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Gene Smith <gds@chartertn.net>
To: insight@sources.redhat.com
Subject: Insight (probably gdb) crashes on thumb-2 startup assembly code
Date: Sat, 26 Feb 2011 07:40:00 -0000	[thread overview]
Message-ID: <ikaaof$332$1@dough.gmane.org> (raw)

When I step into my very early startup code I quickly see this crash in 
gdb or insight:

(gdb) lodnew  #<-- my gdbinit macro to load my code
Loading section .isr_vector, size 0x260 lma 0x0
Loading section .bmark, size 0x24 lma 0x260
Loading section .text, size 0x3888 lma 0x10030000
Loading section .data, size 0x4 lma 0x10033888
Loading section .init_array, size 0x4 lma 0x10040004
Start address 0x0, load size 15124
Transfer rate: 51 KB/sec, 1008 bytes/write.
Loading section .sec1, size 0x10000 lma 0x10030000
Start address 0x0, load size 65536
Transfer rate: 52 KB/sec, 1365 bytes/write.
(gdb) si
0x0000009c in SET_UP ()
(gdb) si
0x0000009e in SET_UP ()
(gdb) si
../../insight_sources/gdb/regcache.c:182: internal-error: register_size: 
Assertion `regnum >= 0 && regnum < (gdbarch_num_regs (gdbarch) + 
gdbarch_num_pseudo_regs (gdbarch))' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n)

This is running the insight or gdb built from a recent insight cvs 
snapshot:GNU gdb (GDB) 7.2.50.20110121-cvs
This GDB was configured as "--host=x86_64-unknown-linux-gnu 
--target=arm-none-eabi".

Assembly code associated with C instructions (also thumb-2) has no 
problem, just the startup pure assembly code.

I can step through the same startup code with insight 6.8.1 with no 
crash but it has problems decoding it as thumb-2.

I suspect this is a gdb problem and not really related to insight, but 
thought I would ask here first.

-gene

             reply	other threads:[~2011-02-26  7:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-26  7:40 Gene Smith [this message]
2011-02-26 18:57 ` Keith Seitz
2011-02-27 19:44   ` Gene Smith

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='ikaaof$332$1@dough.gmane.org' \
    --to=gds@chartertn.net \
    --cc=insight@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).