bug-gdb
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 1600 "unexpected failures" in gdb-weekly-CVS-6.8.50.20090113.tar.bz2


From: Pedro Alves
Subject: Re: 1600 "unexpected failures" in gdb-weekly-CVS-6.8.50.20090113.tar.bz2 (on OpenSolaris 2008.11 using gcc version 4.4.0 20090111)
Date: Sun, 18 Jan 2009 18:18:48 +0000
User-agent: KMail/1.9.10

On Sunday 18 January 2009 11:25:59, address@hidden wrote:
> > Did you consider fixing this, and posting a patch at gdb-patches@ ?
> Not for a moment. All my spare time is devoted to gcc, OpenSolaris and 
> a few other things ...
> 
> There are other people better qualified than I am to ensure that GDB 
> and Binutils is fixed _CORRECTLY_ for
> the OpenSolaris Platform. I would not want to implement fixes to have 
> someone else come along and need
> to fix my fixes. These should be fixed by a better qualified person 
> than me.
> 
> I only have 6 months experience with OpenSolaris and only needed to 
> build gdb to attempt to fix something
> else, not to adopt another GNU project to devote more time to. I 
> volunteer (way) over 10 hours a week to
> the GNU projects so I feel no guilt about not taking on any more work. 
> :) .

Hey, calm down, I wasn't asking you to become solaris
gdb maintainer. :-)  To fix this, all it takes it do something like
adjusting the affected functions to use char buffers and memcpy, instead
of playing tricks with pointers.  A bit of care has to be taken due to
the ifdefery in place, but nothing major.  You're in a good position to
fix it, because, well, you have the compiler handy.  If not taking care of it,
is there somewhere where I can download binaries of a recent enough
gcc that triggers those warnings?  A bugzilla PR with the warning/error log
would also be nice.

> I can enclose the screen output during the check I made
> a few days ago but I can not find the '.log' file. See enclosure.

It's build-dir/gdb/testsuite/gdb.log.  If you run a test with
something like:

make check RUNTESTFLAGS="--debug -v -v foo_test.exp"

you'll find much more debug info in a
build-dir/gdb/testsuite/dbg.log file.

-- 
Pedro Alves




reply via email to

[Prev in Thread] Current Thread [Next in Thread]