[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
gdb still segfaulting on 3.4-current/sparc64
- To: bugs_(_at_)_openbsd_(_dot_)_org
- Subject: gdb still segfaulting on 3.4-current/sparc64
- From: "Alex J. Avriette" <alex_(_at_)_posixnap_(_dot_)_net>
- Date: Sat, 22 Nov 2003 15:47:39 -0500
I mentioned a few months ago, in may, that gdb was segfaulting for
me in 3.3. I upgraded to 3.4 when it was released, and then to 3.4
current when that spate of exploits came out. I'm current as of the
17th.
The original thread is here:
http://archives.neohapsis.com/archives/openbsd/2003-05/1027.html
The results are the same:
Dwarf Error: Cannot find referent at offset 525.
(gdb) bt
Program received signal SIGSEGV, Segmentation fault.
0x16d584 in follow_die_ref ()
(gdb) bt
#0 0x16d584 in follow_die_ref ()
#1 0x16acf8 in die_type ()
#2 0x1689b0 in read_structure_scope ()
#3 0x1682b8 in process_die ()
#4 0x168500 in read_file_scope ()
#5 0x16826c in process_die ()
#6 0x168110 in psymtab_to_symtab_1 ()
#7 0x168038 in dwarf2_psymtab_to_symtab ()
#8 0x128358 in psymtab_to_symtab ()
#9 0x1240a8 in find_pc_symtab ()
#10 0x1240dc in find_pc_line ()
#11 0x10be08 in print_frame_info ()
#12 0x10cd0c in backtrace_command ()
#13 0x1941f8 in execute_command ()
#14 0x1944c0 in command_loop ()
#15 0x19e2c0 in main ()
#16 0x1036d4 in ___start ()
(gdb) list
Dwarf Error: No line number information for compilation unit: /usr/local/src/gnu/egcs/gcc/libgcc2.c.
To reproduce this, you'll have to do something like this:
% sudo gdb gdb
(gdb) r /var/snort/bin/snort
(gdb) r -c /var/snort/snort.conf -u snort -g snort
note that the second (gdb) prompt there is the "nested" gdb. I'm
using Snort 2.0.5 ("build 98") and gcc 2.95.3, the onboard egcs from
OpenBSD. I'd use snort out of ports, except i need a postgresql-
enabled snort.
I also rolled my own postgres, as the version in ports was somewhat
old.
So the flags for postgres were:
--prefix=/var/snort
and the flags for snort were:
--prefix=/var/snort --with-postgresql=/var/snort
Last time around, nobody replied to this message. It's been six months
and one major release, so perhaps somebody is able to take a look at
this presently. A segfaulting gdb is a pretty embarassing thing, I
would think.
Alex
--
alex_(_at_)_posixnap_(_dot_)_net
Alex J. Avriette, Unix Systems Gladiator
Visit your host, monkey.org