This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
Re: gdb/2226: Build failure of GDB CVS with SVN GCC (4.3.0)
- From: Gabriel Dos Reis <gdr at cs dot tamu dot edu>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 13 Feb 2007 01:48:05 -0000
- Subject: Re: gdb/2226: Build failure of GDB CVS with SVN GCC (4.3.0)
- Reply-to: Gabriel Dos Reis <gdr at cs dot tamu dot edu>
The following reply was made to PR gdb/2226; it has been noted by GNATS.
From: Gabriel Dos Reis <gdr@cs.tamu.edu>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-gnats@sources.redhat.com
Subject: Re: gdb/2226: Build failure of GDB CVS with SVN GCC (4.3.0)
Date: 12 Feb 2007 19:39:13 -0600
Daniel Jacobowitz <drow@false.org> writes:
| On Sat, Feb 10, 2007 at 07:04:54AM -0000, gdr@gcc.gnu.org wrote:
| > Attempt to build GDB sources from CVS with SVN GCC (4.3.0, 20070209) results in failure.
| > The build failure is caused by a "may be used uninitialized"
| > that is turned into error because of -Werror in GDB
| > makefile.
|
| ... where? :-) I do not have SVN GCC handy.
Hi Dan,
Thanks for looking into this.
The build failed in p-valprint.c, caused by warnings turned into
errors:
/home/gdr/redhat/combined/gdb/p-valprint.c: In function 'pascal_object_print_value_fields':
/home/gdr/redhat/combined/gdb/p-valprint.c:644: warning: 'tmp_obstack.alloc_failed' may be used uninitialized in this function
/home/gdr/redhat/combined/gdb/p-valprint.c:644: warning: 'tmp_obstack.maybe_empty_object' may be used uninitialized in this function
/home/gdr/redhat/combined/gdb/p-valprint.c:644: warning: 'tmp_obstack.use_extra_arg' may be used uninitialized in this function
/home/gdr/redhat/combined/gdb/p-valprint.c:644: warning: 'tmp_obstack.extra_arg' may be used uninitialized in this function
/home/gdr/redhat/combined/gdb/p-valprint.c:644: warning: 'tmp_obstack.freefun' may be used uninitialized in this function
/home/gdr/redhat/combined/gdb/p-valprint.c:644: warning: 'tmp_obstack.chunkfun' may be used uninitialized in this function
/home/gdr/redhat/combined/gdb/p-valprint.c:644: warning: 'tmp_obstack.alignment_mask' may be used uninitialized in this function
/home/gdr/redhat/combined/gdb/p-valprint.c:644: warning: 'tmp_obstack.temp' may be used uninitialized in this function
/home/gdr/redhat/combined/gdb/p-valprint.c:644: warning: 'tmp_obstack.chunk_limit' may be used uninitialized in this function
/home/gdr/redhat/combined/gdb/p-valprint.c:644: warning: 'tmp_obstack.next_free' may be used uninitialized in this function
/home/gdr/redhat/combined/gdb/p-valprint.c:644: warning: 'tmp_obstack.object_base' may be used uninitialized in this function
/home/gdr/redhat/combined/gdb/p-valprint.c:644: warning: 'tmp_obstack.chunk' may be used uninitialized in this function
/home/gdr/redhat/combined/gdb/p-valprint.c:644: warning: 'tmp_obstack.chunk_size' may be used uninitialized in this function
/home/gdr/redhat/combined/gdb/p-valprint.c: In function 'pascal_object_print_value':
/home/gdr/redhat/combined/gdb/p-valprint.c:813: warning: 'tmp_obstack.alloc_failed' may be used uninitialized in this function
/home/gdr/redhat/combined/gdb/p-valprint.c:813: warning: 'tmp_obstack.maybe_empty_object' may be used uninitialized in this function
/home/gdr/redhat/combined/gdb/p-valprint.c:813: warning: 'tmp_obstack.use_extra_arg' may be used uninitialized in this function
/home/gdr/redhat/combined/gdb/p-valprint.c:813: warning: 'tmp_obstack.extra_arg' may be used uninitialized in this function
/home/gdr/redhat/combined/gdb/p-valprint.c:813: warning: 'tmp_obstack.freefun' may be used uninitialized in this function
/home/gdr/redhat/combined/gdb/p-valprint.c:813: warning: 'tmp_obstack.chunkfun' may be used uninitialized in this function
/home/gdr/redhat/combined/gdb/p-valprint.c:813: warning: 'tmp_obstack.alignment_mask' may be used uninitialized in this function
/home/gdr/redhat/combined/gdb/p-valprint.c:813: warning: 'tmp_obstack.temp' may be used uninitialized in this function
/home/gdr/redhat/combined/gdb/p-valprint.c:813: warning: 'tmp_obstack.chunk_limit' may be used uninitialized in this function
/home/gdr/redhat/combined/gdb/p-valprint.c:813: warning: 'tmp_obstack.next_free' may be used uninitialized in this function
/home/gdr/redhat/combined/gdb/p-valprint.c:813: warning: 'tmp_obstack.object_base' may be used uninitialized in this function
/home/gdr/redhat/combined/gdb/p-valprint.c:813: warning: 'tmp_obstack.chunk' may be used uninitialized in this function
/home/gdr/redhat/combined/gdb/p-valprint.c:813: warning: 'tmp_obstack.chunk_size' may be used uninitialized in this function
BTW, I looked into the docs for information about how to suppress the
build of support for Pascal (and other languages I'm not interested
in). --enable-languages=c++ did not cut it. Is there a "community
knowledge" document somewhere that contains that kind of stuff?
Thanks!
-- Gaby