From: Nick Roberts <nickrob@snap.net.nz>
To: gdb@sources.redhat.com
Subject: internal-error: insert_step_resume_breakpoint_at_sal
Date: Wed, 24 Nov 2004 04:02:00 -0000 [thread overview]
Message-ID: <16804.1142.136766.593493@farnswood.snap.net.nz> (raw)
Debugging emacs in CVS with gdb in CVS, I often get an error if I try to step
through the program after setting a breakpoint:
To reproduce:
gdb emacs
GNU gdb 6.3.50_2004-11-24-cvs
...
(gdb) b Fsplit_window (for example)
(gdb) run
`C-x 2' in Emacs
(gdb) n
infrun.c:2763: internal-error: insert_step_resume_breakpoint_at_sal: Assertion `step_resume_breakpoint == NULL' failed.
A problem internal to GDB has been detected,
GDB then offers to create a core. As few people on this list have CVS Emacs,
I attach it below. There appears to be no problem with older versions of
GDB e.g 5.2.1.
Nick
#0 0x400babf1 in kill () from /lib/libc.so.6
#1 0x400baa05 in raise () from /lib/libc.so.6
#2 0x400bc01b in abort () from /lib/libc.so.6
#3 0x08085630 in internal_vproblem (problem=0x8270950,
file=0x8220d17 "infrun.c", line=2763,
fmt=0x81eed01 "%s: Assertion `%s' failed.", ap=0xbfffed5c " ü!\b")
at utils.c:853
#4 0x08085650 in internal_verror (file=0x8220d17 "infrun.c", line=2763,
fmt=0x81eed01 "%s: Assertion `%s' failed.", ap=0xbfffed5c " ü!\b")
at utils.c:867
#5 0x0808567a in internal_error (file=0x8220d17 "infrun.c", line=2763,
string=0x81eed01 "%s: Assertion `%s' failed.") at utils.c:876
#6 0x080fc68a in insert_step_resume_breakpoint_at_sal (sr_sal=
{symtab = 0x0, section = 0x0, line = 0, pc = 134815836, end = 0},
sr_id=
{stack_addr = 3221220768, code_addr = 134815824, special_addr = 0, stack_ad
dr_p = 1, code_addr_p = 1, special_addr_p = 0}) at infrun.c:2767
#7 0x080fc6ff in insert_step_resume_breakpoint_at_frame (return_frame=0x0)
at infrun.c:2794
#8 0x080faeac in handle_inferior_event (ecs=0xbfffeec0) at infrun.c:2044
#9 0x080fa43b in wait_for_inferior () at infrun.c:986
#10 0x080fa1f7 in proceed (addr=1, siggnal=TARGET_SIGNAL_HUP, step=1)
at infrun.c:806
#11 0x080f79a9 in step_1 (skip_subroutines=1, single_inst=0,
count_string=0x0) at infcmd.c:688
#12 0x080f7833 in next_command (count_string=0x0, from_tty=1)
at infcmd.c:585
#13 0x080afa54 in do_cfunc (c=0x0, args=0x0, from_tty=1)
at cli/cli-decode.c:57
#14 0x080b16f4 in cmd_func (cmd=0x82aef20, args=0x0, from_tty=1)
at cli/cli-decode.c:1627
#15 0x08083632 in execute_command (p=0x8296c51 "", from_tty=1) at top.c:733
#16 0x08106f42 in command_handler (command=0x8296c50 "n") at event-top.c:500
#17 0x08107378 in command_line_handler (rl=0x1 <Address 0x1 out of bounds>)
at event-top.c:793
#18 0x081d6419 in rl_callback_read_char () at callback.c:123
#19 0x081068fa in rl_callback_read_char_wrapper (client_data=0x0)
at event-top.c:166
#20 0x08106e3f in stdin_event_handler (error=0, client_data=0x0)
at event-top.c:416
#21 0x081061dd in handle_file_event (event_file_desc=1075480440)
at event-loop.c:721
#22 0x08105ce4 in process_event () at event-loop.c:334
#23 0x08105d46 in gdb_do_one_event (data=0x0) at event-loop.c:371
#24 0x0808328f in do_catch_errors (uiout=0x82c3f18, data=0x0) at top.c:524
#25 0x08083165 in catcher (func=0x8083280 <do_catch_errors>,
func_uiout=0x82c3f18, func_args=0xbffff2a0, func_val=0xbffff298,
func_caught=0xbffff29c, errstring=0x0, gdberrmsg=0x0, mask=6)
at top.c:431
#26 0x080832d8 in catch_errors (func=0, func_args=0x0,
errstring=0x81ed1dc "", mask=6) at top.c:536
#27 0x080bd243 in tui_command_loop (data=0x0) at tui/tui-interp.c:150
#28 0x08103e19 in current_interp_command_loop () at interps.c:277
#29 0x0807b02a in captured_command_loop (data=0x0) at main.c:91
#30 0x0808328f in do_catch_errors (uiout=0x82c3f18, data=0x0) at top.c:524
#31 0x08083165 in catcher (func=0x8083280 <do_catch_errors>,
func_uiout=0x82c3f18, func_args=0xbffff450, func_val=0xbffff448,
func_caught=0xbffff44c, errstring=0x0, gdberrmsg=0x0, mask=6)
at top.c:431
#32 0x080832d8 in catch_errors (func=0, func_args=0x0,
errstring=0x81ed1dc "", mask=6) at top.c:536
#33 0x0807bb56 in captured_main (data=0x8296970) at main.c:801
#34 0x0808328f in do_catch_errors (uiout=0x8276400, data=0x0) at top.c:524
#35 0x08083165 in catcher (func=0x8083280 <do_catch_errors>,
func_uiout=0x8276400, func_args=0xbffff6f0, func_val=0xbffff6e8,
func_caught=0xbffff6ec, errstring=0x0, gdberrmsg=0x0, mask=6)
at top.c:431
#36 0x080832d8 in catch_errors (func=0, func_args=0x0,
errstring=0x81ed1dc "", mask=6) at top.c:536
#37 0x0807bc72 in gdb_main (args=0x401a8778) at main.c:810
#38 0x0807b00f in main (argc=0, argv=0x0) at gdb.c:35
next reply other threads:[~2004-11-24 3:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-24 4:02 Nick Roberts [this message]
2005-01-16 10:54 ` Nick Roberts
2005-01-18 18:59 ` Andrew Cagney
2005-01-18 21:53 ` Nick Roberts
2005-01-19 15:55 ` Andrew Cagney
2005-01-20 0:59 ` Nick Roberts
2005-01-20 10:23 ` Dave Korn
2005-01-20 10:58 ` Nick Roberts
2005-01-20 17:07 ` Andrew Cagney
2005-01-21 2:47 ` Nick Roberts
2005-01-24 21:59 ` Andrew Cagney
2005-01-26 10:19 ` Nick Roberts
2005-01-26 16:26 ` Andrew Cagney
2005-01-26 20:48 ` Nick Roberts
2005-01-26 21:39 ` Andrew Cagney
2005-01-27 1:02 ` Nick Roberts
2005-02-06 7:16 ` Andrew Cagney
2005-02-06 7:26 ` Andrew Cagney
2005-02-06 20:11 ` Nick Roberts
2005-02-08 16:57 ` Andrew Cagney
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=16804.1142.136766.593493@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--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