This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
corefiles/2140: will not compile under gcc 4.1
- From: zadeck at naturalbridge dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 29 Jun 2006 15:48:55 -0000
- Subject: corefiles/2140: will not compile under gcc 4.1
- Reply-to: zadeck at naturalbridge dot com
>Number: 2140
>Category: corefiles
>Synopsis: will not compile under gcc 4.1
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Thu Jun 29 15:58:01 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator: Kenneth zadeck
>Release: GNU gdb 6.5.50.20060628-cvs
>Organization:
>Environment:
GNU gdb 6.5.50.20060628-cvs
This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-elf".
using gcc (GCC) 4.1.0 (SUSE Linux)
>Description:
Several files do not compile because the compiler gives uninitialized variable warnings and the build options cause the build to stop.
The solution is to simply fix the partially initialized variables.
The uninitilized variable is called tmp_obstack and occurs in cp-valprint.c (cp_print_value_fields, cp_print_value) and p-valprint.c (pascal_object_print_value_fields, pascal_object_print_value)
>How-To-Repeat:
try compiling with a recent version of gcc. Gcc has "improved" it's detection of uninitialized variables.
>Fix:
I added memsets to my files to get them to compile.
This just fixed it for me and may not be the correct solution.
>Release-Note:
>Audit-Trail:
>Unformatted: