This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: backtrace/1797: internal-error: Invalid or unsupported encoding in dwarf2-frame.c
- From: china at thewrittenword dot com (Albert Chin-A-Young)
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 22 Feb 2005 21:28:01 -0000
- Subject: Re: backtrace/1797: internal-error: Invalid or unsupported encoding in dwarf2-frame.c
- Reply-to: china at thewrittenword dot com (Albert Chin-A-Young)
The following reply was made to PR backtrace/1797; it has been noted by GNATS.
From: china@thewrittenword.com (Albert Chin-A-Young)
To: Laurie_E_Williams@raytheon.com
Cc: gdb-gnats@sources.redhat.com, nobody@sources.redhat.com,
gdb-prs@sources.redhat.com
Subject: Re: backtrace/1797: internal-error: Invalid or unsupported encoding in dwarf2-frame.c
Date: Tue, 22 Feb 2005 15:27:21 -0600
On Tue, Feb 22, 2005 at 04:09:50PM -0500, Laurie_E_Williams@raytheon.com wrote:
> This bug report 1797 says it was closed and says "fixed" at the
> bottom, but there is no fix given. I assumed that meant it was
> fixed in gdb 6.3, but I have the same problem with gdb 6.3 running
> on Solaris 8 with gcc 3.4.2.
Then you're not having the same problem. It was fixed in 6.3. The
patch below fixed it for us on 6.2.1 and this patch was merged into
6.3.
Looks like there might be other instances of this bug.
--
albert chin (china@thewrittenword.com)
-- snip snip
--- gdb/dwarf2-frame.c.orig Tue Nov 2 13:49:05 2004
+++ gdb/dwarf2-frame.c Tue Nov 2 14:48:01 2004
@@ -1109,7 +1109,7 @@
internal_error (__FILE__, __LINE__, "Invalid or unsupported encoding");
}
- if ((encoding & 0x0f) == 0x00)
+ if ((encoding & 0x07) == 0x00)
encoding |= encoding_for_size (ptr_len);
switch (encoding & 0x0f)