This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Internal GDB errors with current GDB snapshots and -gdwarf-23
- From: Jim Blandy <jimb at redhat dot com>
- To: Andrew Cagney <ac131313 at ges dot redhat dot com>
- Cc: pavenis at lanet dot lv, djgpp-workers at delorie dot com, gdb at sources dot redhat dot com
- Date: 22 Sep 2002 17:52:39 -0500
- Subject: Re: Internal GDB errors with current GDB snapshots and -gdwarf-23
- References: <3D6E31F2.25704.9E195D@localhost> <3D89F4C2.90809@ges.redhat.com>
The assertion means that the macro debug information contains
something screwey, and GDB didn't detect that when it was read. I'll
try to reproduce the problem.
Thanks for re-posting this bug report. I had missed it the first
time.
Andrew Cagney <ac131313@ges.redhat.com> writes:
> Has anyone had a chance to look at this?
>
> Andrew
> From: pavenis@lanet.lv
> Subject: Internal GDB errors with current GDB snapshots and -gdwarf-23
> To: djgpp-workers@delorie.com
> Cc: gdb@sources.redhat.com
> Date: Thu, 29 Aug 2002 14:38:42 +0300
>
> Built GDB 20020828 snapshot (current tree) for target i586-pc-msdosdjgpp.
> Got following problem. If the sources are compiled using option
> -gdwarf-23 then GDB gets internal error (see below). It doesn't happen
> if -gdwarf-22 is being used.
>
> It is not the first time I see this problem with current GDB tree in some last
> months.
>
> I used gcc-3.2 and binutils-2.13
>
> Andris
>
> GNU gdb 20020829
> Copyright 2002 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=i386-pc-msdosdjgpp --target=djgpp"...
> (gdb) tb main
> macrotab.c:275: gdb-internal-error: compare_locations: Assertion `! included1
> || ! included2' failed.
> An internal GDB error was detected. This may make further
> debugging unreliable. Quit this debugging session? (y or n)
> Create a core file containing the current state of GDB? (y or n) Abort!
> Exiting due to signal SIGABRT
> Raised at eip=00194d46
> eax=ffeb8000 ebx=00000120 ecx=001c0920 edx=00000008 esi=00000001 edi=00000001
> ebp=ffeb80c8 esp=ffeb7ff0 program=C:\DJGPP\BIN\GDB.EXE
> cs: sel=00f7 base=84015000 limit=fff98fff
> ds: sel=00ff base=84015000 limit=fff98fff
> es: sel=00ff base=84015000 limit=fff98fff
> fs: sel=011f base=00018c90 limit=000028ff
> gs: sel=010f base=00000000 limit=0010ffff
> ss: sel=00ff base=84015000 limit=fff98fff
> App stack: [ffeb9000..ffe39000] Exceptn stack: [001ea400..001e84c0]
>
> Call frame traceback EIPs:
> 0x00194c56 __djgpp_traceback_exit+54, file dpmiexcp.c
> 0x00194d46 raise+86, file dpmiexcp.c
> 0x001955a0 abort+32, file abort.c
> 0x00006624 internal_verror+228, file utils.c
> 0x0000665a internal_error+26, file utils.c
> 0x000f0f80 compare_locations+272, file macrotab.c
> 0x000f102d macro_tree_compare+29, file macrotab.c
> 0x0017b748 splay_tree_splay_helper+40, file splay-tree.c
> 0x0017b772 splay_tree_splay_helper+82, file splay-tree.c
> 0x0017b772 splay_tree_splay_helper+82, file splay-tree.c
> 0x0017b772 splay_tree_splay_helper+82, file splay-tree.c
> 0x0017b772 splay_tree_splay_helper+82, file splay-tree.c
> 0x0017b772 splay_tree_splay_helper+82, file splay-tree.c
> 0x0017b772 splay_tree_splay_helper+82, file splay-tree.c
> 0x0017b772 splay_tree_splay_helper+82, file splay-tree.c
> 0x0017b772 splay_tree_splay_helper+82, file splay-tree.c
> 0x0017b884 splay_tree_splay+36, file splay-tree.c
> 0x0017bb04 splay_tree_lookup+20, file splay-tree.c
> 0x000f1564 find_definition+52, file macrotab.c
> 0x000f162a check_for_redefinition+26, file macrotab.c
> 0x000f1732 macro_define_object+50, file macrotab.c
> 0x000fcdb8 parse_macro_definition+120, file dwarf2read.c
> 0x000fd188 dwarf_decode_macros+424, file dwarf2read.c
> 0x000f4cad read_file_scope+541, file dwarf2read.c
> 0x000f470c psymtab_to_symtab_1+284, file dwarf2read.c
> 0x000f4585 dwarf2_psymtab_to_symtab+37, file dwarf2read.c
> 0x00009113 psymtab_to_symtab+67, file symfile.c
> 0x0006b8b6 find_pc_sect_symtab+390, file symtab.c
> 0x0006a996 lookup_symbol_aux+278, file symtab.c
> 0x0006a672 lookup_symbol+82, file symtab.c
> 0x0007ea8e decode_line_1+654, file linespec.c
> 0x0002296f parse_breakpoint_sals+479, file breakpoint.c
> 0x00022ad3 break_command_1+67, file breakpoint.c
> 0x00023775 tbreak_command+21, file breakpoint.c
> 0x0010c604 do_cfunc+20, file cli-decode.c
> 0x0010e4f4 cmd_func+36, file cli-decode.c
> 0x0000345f execute_command+447, file top.c
> 0x0003f9fc command_handler+140, file event-top.c
> 0x0003fe6c command_line_handler+492, file event-top.c
> 0x0015580e rl_callback_read_char+78, file callback.c
> 0x0003f2ea rl_callback_read_char_wrapper+10, file event-top.c
> 0x0003f88e stdin_event_handler+94, file event-top.c
> 0x0008de1c handle_file_event+92, file event-loop.c
> 0x0008d944 process_event+68, file event-loop.c
> 0x0008d996 gdb_do_one_event+54, file event-loop.c
> 0x0000302f do_catch_errors+15, file top.c
> 0x00002f30 catcher+272, file top.c
> 0x00003076 catch_errors+54, file top.c
> 0x0008d9b8 start_event_loop+24, file event-loop.c
> 0x00001624 captured_command_loop+68, file main.c
> 0x0000302f do_catch_errors+15, file top.c
> 0x00002f30 catcher+272, file top.c
> 0x00003076 catch_errors+54, file top.c
> 0x0000234b captured_main+2715, file main.c
> 0x0000302f do_catch_errors+15, file top.c
> 0x00002f30 catcher+272, file top.c
> 0x00003076 catch_errors+54, file top.c
> 0x00002469 main+41, file main.c
> 0x001937f7 __crt1_startup+199, file crt1.c
>
>
>
>
> ----------