Internal Error in GDB (was: ld includes entire archive (.a) when compiling .elf file)

Internal Error in GDB (was: ld includes entire archive (.a) when compiling .elf file)

[Josh Keller]

 
Daniel, for some reason, when I turn on garbage collection, I get the
following error (many, many times) when I run gdb:

Internal error: pc 0x0 in read in psymtab, but not in symtab.

I can still debug my program, but I get these errors all over the place.
I saw a thread back in 2002 titled (Internal error in GDB) initially
posted by Steven Johnson.  I'm not sure what the ultimate resolution
was.  Any ideas?

-Josh

-----Original Message-----
From: Daniel Jacobowitz [mailto:drow@false.org] 
Sent: Friday, March 10, 2006 6:43 PM
To: Josh Keller
Cc: binutils@sourceware.org; Reuben Johnston
Subject: Re: ld includes entire archive (.a) when compiling .elf file

On Fri, Mar 10, 2006 at 06:08:53PM -0500, Josh Keller wrote:
> How will specifying the start of execution with (-e) remove the 
> uncalled functions and unused variables?  Does the ld linker even have

> the capability to automatically remove uncalled functions without 
> having to specify each used section?  I'm sorry if I sound really 
> confused, I'm pretty new to this.  Thanks for your patience.

No, you need that to prevent the linker from removing everything.

--
Daniel Jacobowitz
CodeSourcery

Re: Internal Error in GDB (was: ld includes entire archive (.a) when compiling .elf file)

[Daniel Jacobowitz]

On Fri, Apr 07, 2006 at 10:15:26AM -0400, Josh Keller wrote:
>  
> Daniel, for some reason, when I turn on garbage collection, I get the
> following error (many, many times) when I run gdb:
> 
> Internal error: pc 0x0 in read in psymtab, but not in symtab.

Code is being discarded, but not its debug information.

Alan Modra was doing some work on this, but ran into a snag, IIRC.

> I can still debug my program, but I get these errors all over the place.
> I saw a thread back in 2002 titled (Internal error in GDB) initially
> posted by Steven Johnson.  I'm not sure what the ultimate resolution
> was.  Any ideas?

No relation to this problem most likely.

-- 
Daniel Jacobowitz
CodeSourcery

Re: Internal Error in GDB (was: ld includes entire archive (.a) when compiling .elf file)

[Alan Modra]

On Fri, Apr 07, 2006 at 10:17:44AM -0400, Daniel Jacobowitz wrote:
> Code is being discarded, but not its debug information.
> 
> Alan Modra was doing some work on this, but ran into a snag, IIRC.

The snag is that it is more work than I originally thought.  :)

I don't think there is a major technical problem, but of course I might
run into a real snag when I find time to do some further work.

-- 
Alan Modra
IBM OzLabs - Linux Technology Centre

RE: Internal Error in GDB (was: ld includes entire archive (.a) when compiling .elf file)

[Dave Korn]

On 07 April 2006 15:35, Daniel Jacobowitz wrote:

> On Fri, Apr 07, 2006 at 10:33:46AM -0400, Josh Keller wrote:
>> Is there any way that I can disable these messages so that I can debug
>> more easily?
> 
> I don't think so.

  :)  Why, are you saying that building gdb from source isn't easy?

  /src/gdb/symtab.c, line 1919:

---------------------------------------<snip>
  s = NULL;
  ps = find_pc_sect_psymtab (pc, section);
  if (ps)
    {
      if (ps->readin)
	/* Might want to error() here (in case symtab is corrupt and
	   will cause a core dump), but maybe we can successfully
	   continue, so let's not.  */
	warning (_("\
(Internal error: pc 0x%s in read in psymtab, but not in symtab.)\n"),
		 paddr_nz (pc));
      s = PSYMTAB_TO_SYMTAB (ps);
    }
  return (s);
---------------------------------------<snip>

  Yow.  If you delete the warning() call, watch out for the un-braced if
conditional, it's easy to miss one of those when there's a comment in the way
like that.


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....

Re: Internal Error in GDB (was: ld includes entire archive (.a) when compiling .elf file)

[Daniel Jacobowitz]

On Fri, Apr 07, 2006 at 10:33:46AM -0400, Josh Keller wrote:
> Is there any way that I can disable these messages so that I can debug
> more easily?

I don't think so.

-- 
Daniel Jacobowitz
CodeSourcery

RE: Internal Error in GDB (was: ld includes entire archive (.a) when compiling .elf file)

[Josh Keller]

Is there any way that I can disable these messages so that I can debug
more easily?
-Josh 

-----Original Message-----
From: Daniel Jacobowitz [mailto:drow@false.org] 
Sent: Friday, April 07, 2006 10:18 AM
To: Josh Keller
Cc: binutils@sourceware.org; Reuben Johnston
Subject: Re: Internal Error in GDB (was: ld includes entire archive (.a)
when compiling .elf file)

On Fri, Apr 07, 2006 at 10:15:26AM -0400, Josh Keller wrote:
>  
> Daniel, for some reason, when I turn on garbage collection, I get the 
> following error (many, many times) when I run gdb:
> 
> Internal error: pc 0x0 in read in psymtab, but not in symtab.

Code is being discarded, but not its debug information.

Alan Modra was doing some work on this, but ran into a snag, IIRC.

> I can still debug my program, but I get these errors all over the
place.
> I saw a thread back in 2002 titled (Internal error in GDB) initially 
> posted by Steven Johnson.  I'm not sure what the ultimate resolution 
> was.  Any ideas?

No relation to this problem most likely.

--
Daniel Jacobowitz
CodeSourcery