From: Michael Veksler <VEKSLER@il.ibm.com>
To: David Frager <frager@nortelnetworks.com>
Cc: gdb@sources.redhat.com
Subject: Re: Internal GDB error
Date: Wed, 07 Apr 2004 19:52:00 -0000 [thread overview]
Message-ID: <OF675455AD.F0DA994D-ONC2256E6F.006C4327-C2256E6F.006D1F3F@il.ibm.com> (raw)
In-Reply-To: <20040407085539.1a626063.frager@nortelnetworks.com>
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
next prev parent reply other threads:[~2004-04-07 19:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 4:43 Michael Veksler
2004-04-07 14:02 ` David Frager
2004-04-07 19:52 ` Michael Veksler [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-22 17:49 Blazquez Fernandez, Miguel Angel
2004-04-05 14:01 David Frager
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=OF675455AD.F0DA994D-ONC2256E6F.006C4327-C2256E6F.006D1F3F@il.ibm.com \
--to=veksler@il.ibm.com \
--cc=frager@nortelnetworks.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).