Bug 10950 - get_frame_block: Assertion `bl != NULL' failed
Summary: get_frame_block: Assertion `bl != NULL' failed
Status: RESOLVED WORKSFORME
Alias: None
Product: gdb
Classification: Unclassified
Component: gdb (show other bugs)
Version: 7.0
: P2 normal
Target Milestone: 7.1
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-13 10:34 UTC by Domen Puncer
Modified: 2010-01-26 07:14 UTC (History)
1 user (show)

See Also:
Host: x86_64-unknown-linux-gnu
Target: arm-none-eabi
Build: == host?
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Domen Puncer 2009-11-13 10:34:56 UTC 
Hello,

I've just got this one, and I have no idea how to reproduce it. I suspect it has
to do with symbols reload.

GNU gdb (GDB) 7.0.50.20091110
This GDB was configured as "--host=x86_64-unknown-linux-gnu --target=arm-none-eabi".

`/home/domen/stm32/cortex-m3_trinity/cortex-linux.elf' has changed; re-reading
symbols.
blockframe.c:84: internal-error: get_frame_block: Assertion `bl != NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) [answered Y; input not from terminal]
blockframe.c:84: internal-error: get_frame_block: Assertion `bl != NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) [answered Y; input not from terminal]
Aborted (core dumped)
Comment 1 Domen Puncer 2009-11-13 10:37:04 UTC 
Oh, no, sorry,
this one was from
GNU gdb (GDB) 7.0.50.20090924

I'll see if I hit it with a recent snapshot too.
Comment 2 Tom Tromey 2010-01-25 18:41:19 UTC 
A stack trace of gdb itself might be useful.
Comment 3 Domen Puncer 2010-01-26 07:14:36 UTC 
Hmm... with more recent snapshots I've been unable to reproduce this.