Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: David Frager <frager@nortelnetworks.com>
To: gdb@sources.redhat.com
Subject: Internal GDB error
Date: Mon, 05 Apr 2004 14:01:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0404050900210.19218-100000@crchi02q.us.nortel.com> (raw)

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)



             reply	other threads:[~2004-04-05 14:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-05 14:01 David Frager [this message]
2004-04-07  4:43 Michael Veksler
2004-04-07 14:02 ` David Frager
2004-04-07 19:52   ` Michael Veksler
2004-04-22 17:49 Blazquez Fernandez, Miguel Angel

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=Pine.LNX.4.44.0404050900210.19218-100000@crchi02q.us.nortel.com \
    --to=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