From: Joost VandeVondele <jv244@hermes.cam.ac.uk>
To: Vincent Rubiolo <vincent.rubiolo@windriver.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdb 6.3 segfault at stack.c:294
Date: Mon, 06 Jun 2005 13:58:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.60.0506061457350.17046@hermes-1.csi.cam.ac.uk> (raw)
In-Reply-To: <42A4551C.5090107@windriver.com>
That's what I get:
(gdb) bt
#0 print_frame_args (func=Variable "func" is not available.
) at stack.c:294
#1 0x08110cd5 in print_args_stub (args=0xbfffdba4) at stack.c:402
#2 0x08084d81 in do_catch_errors (uiout=0x82e37e0, data=0x0) at top.c:524
#3 0x08084beb in catcher (func=0x8084d70 <do_catch_errors>,
func_uiout=0x82e37e0, func_args=0xbfffdac8, func_val=0xbfffdad4,
func_caught=0xbfffdad0, errstring=0x82154f0 "", gdberrmsg=0x0, mask=6)
at top.c:431
#4 0x08084dd6 in catch_errors (func=0, func_args=0x0, errstring=0x0,
mask=0) at top.c:536
#5 0x081114f6 in print_frame_info (fi=0x82d2850, print_level=0,
print_what=SRC_AND_LOC, print_args=1) at stack.c:654
#6 0x081116a8 in print_stack_frame_stub (args=0x0) at stack.c:135
#7 0x08084d81 in do_catch_errors (uiout=0x82e37e0, data=0x0) at top.c:524
#8 0x08084beb in catcher (func=0x8084d70 <do_catch_errors>,
func_uiout=0x82e37e0, func_args=0xbfffdcf8, func_val=0xbfffdd04,
func_caught=0xbfffdd00, errstring=0x82154f0 "", gdberrmsg=0x0, mask=6)
at top.c:431
#9 0x08084dd6 in catch_errors (func=0, func_args=0x0, errstring=0x0,
mask=0) at top.c:536
#10 0x08110844 in print_stack_frame (fi=0x0, print_level=0,
print_what=LOCATION) at stack.c:156
#11 0x0810ac1b in normal_stop () at infrun.c:3017
#12 0x0810d69b in proceed (addr=4294967295, siggnal=TARGET_SIGNAL_0,
step=0) at infrun.c:815
#13 0x08107450 in run_command (args=0x0, from_tty=1) at infcmd.c:481
#14 0x080851d0 in execute_command (p=0x82aeedb "", from_tty=1) at
top.c:733
#15 0x08118044 in command_handler (command=0x82aeed8 "") at
event-top.c:500
#16 0x081184e5 in command_line_handler (rl=0x83e06f0 "8~2\b") at
event-top.c:793
#17 0x081fdf70 in rl_callback_read_char () at callback.c:123
#18 0x081179cb in rl_callback_read_char_wrapper (client_data=0x0) at
event-top.c:166
#19 0x08117257 in handle_file_event (event_file_desc=0) at
event-loop.c:721
#20 0x08116cf4 in process_event () at event-loop.c:334
#21 0x08117590 in gdb_do_one_event (data=0x0) at event-loop.c:371
#22 0x08084d81 in do_catch_errors (uiout=0x82e37e0, data=0x0) at top.c:524
#23 0x08084beb in catcher (func=0x8084d70 <do_catch_errors>,
func_uiout=0x82e37e0, func_args=0xbfffe098, func_val=0xbfffe0a4,
func_caught=0xbfffe0a0, errstring=0x82154f0 "", gdberrmsg=0x0, mask=6)
at top.c:431
#24 0x08084dd6 in catch_errors (func=0, func_args=0x0, errstring=0x0,
mask=0) at top.c:536
#25 0x080c50f4 in tui_command_loop (data=0x0) at ./tui/tui-interp.c:150
#26 0x08114b7f in current_interp_command_loop () at interps.c:277
#27 0x0807ae8b in captured_command_loop (data=0x0) at ./main.c:91
#28 0x08084d81 in do_catch_errors (uiout=0x82e37e0, data=0x0) at top.c:524
#29 0x08084beb in catcher (func=0x8084d70 <do_catch_errors>,
func_uiout=0x82e37e0, func_args=0xbfffe208, func_val=0xbfffe214,
func_caught=0xbfffe210, errstring=0x82154f0 "", gdberrmsg=0x0, mask=6)
at top.c:431
#30 0x08084dd6 in catch_errors (func=0, func_args=0x0, errstring=0x0,
mask=0) at top.c:536
#31 0x0807b5f4 in captured_main (data=0x0) at ./main.c:801
#32 0x08084d81 in do_catch_errors (uiout=0x828cf40, data=0x0) at top.c:524
#33 0x08084beb in catcher (func=0x8084d70 <do_catch_errors>,
func_uiout=0x828cf40, func_args=0xbfffe488, func_val=0xbfffe494,
func_caught=0xbfffe490, errstring=0x82154f0 "", gdberrmsg=0x0, mask=6)
at top.c:431
#34 0x08084dd6 in catch_errors (func=0, func_args=0x0, errstring=0x0,
mask=0) at top.c:536
#35 0x0807aef3 in gdb_main (args=0x0) at ./main.c:810
#36 0x0807ae71 in main (argc=0, argv=0x0) at gdb.c:35
next prev parent reply other threads:[~2005-06-06 13:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-06 13:44 Joost VandeVondele
2005-06-06 13:53 ` Vincent Rubiolo
2005-06-06 13:58 ` Joost VandeVondele [this message]
2005-06-06 13:59 ` Daniel Jacobowitz
2005-06-06 14:06 ` Joost VandeVondele
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=Pine.LNX.4.60.0506061457350.17046@hermes-1.csi.cam.ac.uk \
--to=jv244@hermes.cam.ac.uk \
--cc=gdb@sources.redhat.com \
--cc=vincent.rubiolo@windriver.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