This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: gdb 5.0 "ia64-unknown-linux" segv error
- To: gjertsen at us dot ibm dot com
- Subject: Re: gdb 5.0 "ia64-unknown-linux" segv error
- From: Kevin Buettner <kevinb at cygnus dot com>
- Date: Sat, 9 Dec 2000 16:05:41 -0700
- Cc: bug-gdb at gnu dot org, gdb at sources dot redhat dot com
- References: <852569AF.0071239B.00@d54mta01.raleigh.ibm.com>
On Dec 8, 3:34pm, gjertsen@us.ibm.com wrote:
> I've transferred the ~24Mb file, testcase.tar.gz, over to the incoming
> location.
>
> The name/size information is:
>
> -rw-rw-r-- 1 gjertsen gjertsen 24473202 Dec 8 15:33 testcase.tar.gz
>
> tar file contents:
> -rwxrwxr-x 1 gjertsen gjertsen 74072196 Dec 8 15:30 mmfsd
> -rw-rw-r-- 1 gjertsen gjertsen 3158277 Dec 8 15:30 mmfsd.map
Thanks for the test case. I am able to reproduce the bug that you
reported. I've done some investigation and I now wonder what tools
you used to create mmfsd. (I.e, I wonder if the bug is actually in
the compiler.) I've used "readelf -wi" to look at the debugging
symbols in mmfsd and I see the following:
<1><96d50>: Abbrev Number: 12 (DW_TAG_typedef)
DW_AT_name : ulong
DW_AT_decl_file : 12
DW_AT_decl_line : 59
DW_AT_type : <96d50>
I'm not a DWARF2 expert, but it looks to me like the above is a
self referential typedef. This would explain why you're seeing
the infinite recursion in dwarf2read.c.
I've cc'd the gdb discussion list so that others more expert than
myself regarding DWARF2 can weigh in on this problem. For those
of you who missed the original bug report, it may be found at:
http://mail.gnu.org/pipermail/bug-gdb/2000-December/001542.html
Kevin