Re: SEGV running gdb-6.7 on Tru64 UNIX 5.1

Albert Chin
2007-10-18T16:52:42Z

On Wed, Oct 17, 2007 at 08:19:54PM -0700, Joel Brobecker wrote:
> > Anyone running 6.7 successfully on Tru64 UNIX 5.1? gdb-6.6 Worked ok.
>
> I am able to run it through your example. However, I did build the
> executable using gcc, not cc. That's probably where the difference is.

I built with gcc-3.4.3 and still get a SEGV with the 'list' command,
but the ladebug backtrace is different:
>0 0x1200a802c in target_write_with_progress(ops=0x1401297c0, object=TARGET_OBJECT_SPU, annex=0x0, buf=0x0, offset=4831842700, len=4831819312, progress=0x11fffb6b0, baton=0x11fffb630) "target.c":1452
#1 0x1200a7ff4 in target_write_with_progress(ops=0x1401297c0, object=TARGET_OBJECT_SPU, annex=0x0, buf=0x0, offset=4831842700, len=4831819312, progress=0x11fffb6b0, baton=0x11fffb630) "target.c":1439

> > >0 0x120125920 in symbol_found(funfirstline=1, canonical=0x0, copy=0x1401778d0="main", sym=0x14014d7c0, file_symtab=0x0, sym_symtab=0x0) "linespec.c":1786
>
> The problem here is that both file_symtab and sym_symtab are NULL.
> Looking at the frame just above it:
>
> > #1 0x120125744 in decode_variable(copy=0x1401778d0="main", funfirstline=1, canonical=0x0, file_symtab=0x0, not_found_ptr=0x0) "linespec.c":1737
>
> Apparently, lookup_symbol found a symbol for "main", but did not
> return the associated symtab.
>
> You'll probably need to debug GDB to find out why
> lookup_symbol_in_language set the symtab to NULL...

Ok, I'll have to do some digging. Thanks.

--
albert chin (china@thewrittenword.com)