Internal GDB error

Internal GDB error

[David Frager]

I am having problems running gdb in an AIX 4.3.3 environment.  I can set 
tracepoints, however, if I attempt to invoke any additional actions (i.e., step, 
next, etc.), I receive the internal gdb error below:

Any recommendations to help determine if this is a gdb bug or local environment 
issue would be appreciated.

My environment is:
AIX 4.3.3 running on a Motorola Powerstac
	
GNU gdb 6.0
Copyright 2003 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 
"powerpc-ibm-aix4.3.3.0".

g++ (GCC) 3.3
Copyright (C) 2003 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO 
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Breakpoint 1, gsmFmInterface::getFileList(fileCriteria const&) (this=0x2ff229c8, 
criteria=@0x2ff22b08)
    at gsmFmInterface.C:168
168       if(!criteria.getRstrDirOnly())
Current language:  auto; currently c++
(gdb) n
gdbtypes.c:533: internal-error: make_cv_type: Assertion `TYPE_OBJFILE (*typeptr) 
== TYPE_OBJFILE (type) || TYPE_STUB (*typeptr)' failed. A problem internal to 
GDB has been detected, further debugging may prove unreliable. Quit this 
debugging session? (y or n) y

gdbtypes.c:533: internal-error: make_cv_type: Assertion `TYPE_OBJFILE (*typeptr) 
== TYPE_OBJFILE (type) || TYPE_STUB (*typeptr)' failed. A problem internal to 
GDB has been detected, further debugging may prove unreliable. Create a core 
file of GDB? (y or n) y IOT/Abort trap(coredump)

Re: Internal GDB error

[Michael Veksler]

Check PR 1170:

http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=1170

Because of a bug in gcc or in /bin/as, bad debug information is generated.
Instead of terminating gracefully, GDB crashes the way it does. The PR
describes a work-around that you can implement in GCC.

Disclaimer:
I am neither familiar with gdb, gcc nor with /bin/as internals and
interfaces.
All I wanted is to debug my code in this setup....

David Frager:
> I am having problems running gdb in an AIX 4.3.3 environment.  I can set
> tracepoints, however, if I attempt to invoke any additional actions
(i.e., step,
> next, etc.), I receive the internal gdb error below:
>
> Any recommendations to help determine if this is a gdb bug or local
environment
> issue would be appreciated.

My environment is:
AIX 4.3.3 running on a Motorola Powerstac

GNU gdb 6.0
Copyright 2003 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
"powerpc-ibm-aix4.3.3.0".

g++ (GCC) 3.3
Copyright (C) 2003 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Breakpoint 1, gsmFmInterface::getFileList(fileCriteria const&)
(this=0x2ff229c8,
criteria=@0x2ff22b08)
    at gsmFmInterface.C:168
168       if(!criteria.getRstrDirOnly())
Current language:  auto; currently c++
(gdb) n
gdbtypes.c:533: internal-error: make_cv_type: Assertion `TYPE_OBJFILE
(*typeptr)
== TYPE_OBJFILE (type) || TYPE_STUB (*typeptr)' failed. A problem internal
to
GDB has been detected, further debugging may prove unreliable. Quit this
debugging session? (y or n) y

gdbtypes.c:533: internal-error: make_cv_type: Assertion `TYPE_OBJFILE
(*typeptr)
== TYPE_OBJFILE (type) || TYPE_STUB (*typeptr)' failed. A problem internal
to
GDB has been detected, further debugging may prove unreliable. Create a
core
file of GDB? (y or n) y IOT/Abort trap(coredump)

Re: Internal GDB error

[David Frager]

Thank you for the information...I will rebuild gcc and give it a try

Is there a bug report open against gcc for this issue?
On Tue, 6 Apr 2004 23:41:29 -0500 
Michael Veksler <VEKSLER@il.ibm.com> wrote:

> Check PR 1170:
> 
> http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&dat
> abase=gdb&pr=1170
> 
> Because of a bug in gcc or in /bin/as, bad debug information is
> generated.
> Instead of terminating gracefully, GDB crashes the way it does. The PR
> describes a work-around that you can implement in GCC.
> 
> Disclaimer:
> I am neither familiar with gdb, gcc nor with /bin/as internals and
> interfaces.
> All I wanted is to debug my code in this setup....
> 
> David Frager:
> > I am having problems running gdb in an AIX 4.3.3 environment.  I can
> set
> > tracepoints, however, if I attempt to invoke any additional actions
> (i.e., step,
> > next, etc.), I receive the internal gdb error below:
> >
> > Any recommendations to help determine if this is a gdb bug or local
> environment
> > issue would be appreciated.
> 
> My environment is:
> AIX 4.3.3 running on a Motorola Powerstac
> 
> GNU gdb 6.0
> Copyright 2003 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
> "powerpc-ibm-aix4.3.3.0".
> 
> g++ (GCC) 3.3
> Copyright (C) 2003 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is
> NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
> PURPOSE.
> 
> Breakpoint 1, gsmFmInterface::getFileList(fileCriteria const&)
> (this=0x2ff229c8,
> criteria=@0x2ff22b08)
>     at gsmFmInterface.C:168
> 168       if(!criteria.getRstrDirOnly())
> Current language:  auto; currently c++
> (gdb) n
> gdbtypes.c:533: internal-error: make_cv_type: Assertion `TYPE_OBJFILE
> (*typeptr)
> == TYPE_OBJFILE (type) || TYPE_STUB (*typeptr)' failed. A problem
> internal
> to
> GDB has been detected, further debugging may prove unreliable. Quit this
> debugging session? (y or n) y
> 
> gdbtypes.c:533: internal-error: make_cv_type: Assertion `TYPE_OBJFILE
> (*typeptr)
> == TYPE_OBJFILE (type) || TYPE_STUB (*typeptr)' failed. A problem
> internal
> to
> GDB has been detected, further debugging may prove unreliable. Create a
> core
> file of GDB? (y or n) y IOT/Abort trap(coredump)
> 
> 
> 
> 
> 


-- 
David Frager
UMTS OAM Architect
frager@nortelnetworks.com
External:  (972) 685-2383      ESN:  445-2383

Re: Internal GDB error

[Michael Veksler]

No, there was no PR filed to gcc. I was not sure if it was /bin/as or a gcc
bug. Instead of opening a PR, I contacted people that can eventually
figure out who's fault it is, and I nag them every other month (I guess
time is up to nag them again). It seems more productive to me.

Anyway, it seems that GDB is a better place to keep this PR for
the moment, because it is more natural to look up the PR there.
So if anyone wants to find out what is the cause behind this
"Internal GDB error" she will find it in GDB's database.




                                                                                                                      
                      David Frager                                                                                    
                      <frager@nortelnet        To:       Michael Veksler/Haifa/IBM@IBMIL                              
                      works.com>               cc:       "David Frager" <frager@nortelnetworks.com>,                  
                      Sent by:                  gdb@sources.redhat.com                                                
                      gdb-owner@sources        Subject:  Re: Internal GDB error                                       
                      .redhat.com                                                                                     
                                                                                                                      
                                                                                                                      
                      2004-04-07 16:55                                                                                
                                                                                                                      




Thank you for the information...I will rebuild gcc and give it a try

Is there a bug report open against gcc for this issue?
On Tue, 6 Apr 2004 23:41:29 -0500
Michael Veksler <VEKSLER@il.ibm.com> wrote:

> Check PR 1170:
>
> http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&dat
> abase=gdb&pr=1170
>
> Because of a bug in gcc or in /bin/as, bad debug information is
> generated.
> Instead of terminating gracefully, GDB crashes the way it does. The PR
> describes a work-around that you can implement in GCC.
>
> Disclaimer:
> I am neither familiar with gdb, gcc nor with /bin/as internals and
> interfaces.
> All I wanted is to debug my code in this setup....
>
> David Frager:
> > I am having problems running gdb in an AIX 4.3.3 environment.  I can
> set
> > tracepoints, however, if I attempt to invoke any additional actions
> (i.e., step,
> > next, etc.), I receive the internal gdb error below:
> >
> > Any recommendations to help determine if this is a gdb bug or local
> environment
> > issue would be appreciated.
>
> My environment is:
> AIX 4.3.3 running on a Motorola Powerstac
>
> GNU gdb 6.0
> Copyright 2003 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
> "powerpc-ibm-aix4.3.3.0".
>
> g++ (GCC) 3.3
> Copyright (C) 2003 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is
> NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
> PURPOSE.
>
> Breakpoint 1, gsmFmInterface::getFileList(fileCriteria const&)
> (this=0x2ff229c8,
> criteria=@0x2ff22b08)
>     at gsmFmInterface.C:168
> 168       if(!criteria.getRstrDirOnly())
> Current language:  auto; currently c++
> (gdb) n
> gdbtypes.c:533: internal-error: make_cv_type: Assertion `TYPE_OBJFILE
> (*typeptr)
> == TYPE_OBJFILE (type) || TYPE_STUB (*typeptr)' failed. A problem
> internal
> to
> GDB has been detected, further debugging may prove unreliable. Quit this
> debugging session? (y or n) y
>
> gdbtypes.c:533: internal-error: make_cv_type: Assertion `TYPE_OBJFILE
> (*typeptr)
> == TYPE_OBJFILE (type) || TYPE_STUB (*typeptr)' failed. A problem
> internal
> to
> GDB has been detected, further debugging may prove unreliable. Create a
> core
> file of GDB? (y or n) y IOT/Abort trap(coredump)
>
>
>
>
>


--
David Frager
UMTS OAM Architect
frager@nortelnetworks.com
External:  (972) 685-2383      ESN:  445-2383

Re: Internal GDB error

[Blazquez Fernandez, Miguel Angel]

Hi,

I am having the same problem.

I am able to reproduce the problem using the example in PR-1170

My environment is:

AIX 4.3.3 running on a AIX powerpc box.

G++ compiler 3.3.1

I have just tried using gdb 5.3, 6.0 and 6.1 and the problem still appears.

I would like to try the work-around for the gcc compiler but I am not sure
about the changes I have to add to the file gcc/dbxout.c

Had anyone wrote those changes??? So, I can cut and paste in order to
rebuild gcc 3.3.1

Thank you in advance.

MAB