This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: gdb/1628: (gdb) file ... fails internal-error gdb 6.1 gcc 3.3.2 solaris2.7
- From: Mark Kettenis <kettenis at chello dot nl>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 29 Apr 2004 08:18:13 -0000
- Subject: Re: gdb/1628: (gdb) file ... fails internal-error gdb 6.1 gcc 3.3.2 solaris2.7
- Reply-to: Mark Kettenis <kettenis at chello dot nl>
The following reply was made to PR gdb/1628; it has been noted by GNATS.
From: Mark Kettenis <kettenis@chello.nl>
To: jim_ziegler@ltx.com
Cc: gdb-gnats@sources.redhat.com
Subject: Re: gdb/1628: (gdb) file ... fails internal-error gdb 6.1 gcc
3.3.2 solaris2.7
Date: Thu, 29 Apr 2004 10:12:36 +0200 (CEST)
From: Jim Ziegler <jim_ziegler@ltx.com>
Date: Wed, 28 Apr 2004 16:46:51 -0400
The problem is that while processing the dwarf2 data, a cie is
found with encoding 0x74, then , when we try to process an fde, we
fail in read_encoded_value because 0x74 is not recognized. Is
this a valid encoding? Or is this actually a g++ problem?
AFAICT 0x74 isn't a valid encoding, so something is amiss. Either the
generated DWARF2 is wrong or GDB looses track and mis-interprets the
data. Do you have a (preferably small) executable that exhibits this
problem that you can post?
Thanks,
Mark