symtab/2005: info line seems to crash in gdb 6.3

Sven Krueger
Mon Sep 12 14:38:00 GMT 2005

The following reply was made to PR symtab/2005; it has been noted by GNATS.

From: Sven Krueger <>
Cc: Daniel Jacobowitz <>
Subject: Re: symtab/2005: info line seems to crash in gdb 6.3
Date: Wed, 7 Sep 2005 08:04:00 +0200

 > I can't reproduce this.  Can you get a backtrace?
 if I start a gdb in another gdb and use this one for debugging the simple 
 Hello World program I get the following backtrace:
 Starting program: /usr/home/krueger/test/gdb/hw1
 Detaching after fork from child process 3023.
 Detaching after fork from child process 3024.
 Reading symbols from shared object read from target memory...done.
 Loaded system supplied DSO at 0xbd0000
 Hello world
 Program received signal SIGINT, Interrupt.
 0x00bd0402 in __kernel_vsyscall ()
 (gdb) info line main
 Program received signal SIGSEGV, Segmentation fault.
 0x00b10926 in free () from /lib/
 (gdb) bt
 #0  0x00b10926 in free () from /lib/
 #1  0x080f4ca1 in find_line_pc_range ()
 #2  0x080df3a4 in print_source_lines ()
 #3  0x08084da2 in execute_command ()
 #4  0x08112c94 in async_disable_stdin ()
 #5  0x08113109 in async_disable_stdin ()
 #6  0x081ede7d in rl_callback_read_char ()
 #7  0x081125bb in delete_timer ()
 #8  0x08111e6e in delete_file_handler ()
 #9  0x08111952 in standard_macro_lookup ()
 #10 0x08112197 in gdb_do_one_event ()
 #11 0x08084834 in throw_exception ()
 #12 0x080849ed in catch_errors ()
 #13 0x080c2799 in _initialize_tui_hooks ()
 #14 0x0810f953 in current_interp_command_loop ()
 #15 0x0807b4fb in main ()
 Setting MALLOC_CHECK_ to a value different to 0 will result in an abort 
 instead of a seg fault. The backtrace is equal to the one above except for 
 some additional malloc check routines on the top of the stack.

More information about the Gdb-prs mailing list