From: lars-henrik.ivarsson@mecel.se
To: gdb@sources.redhat.com
Subject: Insight assertions (arm-elf)
Date: Thu, 13 Feb 2003 06:21:00 -0000 [thread overview]
Message-ID: <20030213062100.vOdKbcHCVJ5j2drkGfI_q4L5WyqwKgNNpb5nIdS_RzQ@z> (raw)
Hi,
I have succesfully build Insight-20030210 with the patch and fix posted
here the last days.
However when I run the debugger i get an assertion in frame.c (see log
below).
I'm running against an ARM Integrator board with RedBoot installed
Is this a known problem? Any workaround available?
$ arm-elf-insight.exe -nw
GNU gdb 20030210
Copyright 2003 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 "--host=i686-pc-cygwin --target=arm-elf".
(gdb) set remotebaud 38400
(gdb) target remote /dev/ttyS0
Remote debugging using /dev/ttyS0
/src/gdb/insight+dejagnu-20030210/gdb/frame.c:1439: internal-error: deprecated_update_frame_pc_hack:
Assertion `frame->next != NULL' failed.
A problem internal to GDB has been detected. Further
debugging may prove unreliable.
Quit this debugging session? (y or n) n
Create a core file of GDB? (y or n) n
0x24008498 in ?? ()
(gdb) load /ecos-d/arm/ecos/Testapp/hello
Loading section .rom_vectors, size 0x40 lma 0x40000
Loading section .text, size 0x78f0 lma 0x40040
Loading section .rodata, size 0x2dc lma 0x47930
Loading section .data, size 0x32c lma 0x47c0c
Start address 0x40040, load size 32568
Transfer rate: 26054 bits/sec, 298 bytes/write.
(gdb)
According to the Insight people this is not an Insight problem but rather a gdb problem.
Best regards
Lars-Henrik
____________________________
Lars-Henrik Ivarsson
Software Engineer
Mecel AB
Phone: +46 31 720 44 38
Mobile: +46 70 431 32 38
Fax: +46 31 720 44 90
E-mail: lars-henrik.ivarsson@mecel.se
Web: www.mecel.se
____________________________
next reply other threads:[~2003-02-13 6:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 6:21 lars-henrik.ivarsson [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-13 6:21 lars-henrik.ivarsson
2003-02-13 6:21 lars-henrik.ivarsson
2003-02-13 6:21 lars-henrik.ivarsson
2003-02-13 6:21 lars-henrik.ivarsson
2003-02-13 6:21 lars-henrik.ivarsson
2003-02-13 6:21 lars-henrik.ivarsson
2003-02-13 6:21 lars-henrik.ivarsson
2003-02-13 6:21 lars-henrik.ivarsson
2003-02-13 6:21 lars-henrik.ivarsson
2003-02-13 6:21 lars-henrik.ivarsson
2003-02-13 6:21 lars-henrik.ivarsson
2003-02-13 6:21 lars-henrik.ivarsson
2003-02-13 6:21 lars-henrik.ivarsson
2003-02-13 6:21 lars-henrik.ivarsson
2003-02-13 6:21 lars-henrik.ivarsson
2003-02-13 6:21 lars-henrik.ivarsson
2003-02-13 6:21 lars-henrik.ivarsson
2003-02-13 6:21 lars-henrik.ivarsson
2003-02-13 6:21 lars-henrik.ivarsson
2003-02-13 6:21 lars-henrik.ivarsson
2003-02-13 6:21 lars-henrik.ivarsson
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=20030213062100.vOdKbcHCVJ5j2drkGfI_q4L5WyqwKgNNpb5nIdS_RzQ@z \
--to=lars-henrik.ivarsson@mecel.se \
--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