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)

[rob1weld]

-----Original Message-----
From: Pedro Alves <address@hidden>
To: address@hidden
Cc: address@hidden
Sent: Sun, 18 Jan 2009 10:18 am
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)

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_ ...
> > ...
> > 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 ...  :) .

> Hey, calm down, I wasn't asking you to become solaris gdb maintainer. 
:-)

I meant fixing all 1600 Bugs.


> 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.

So this takes me as little time as possible ...
Do you have a patch ?


> 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?

I can do it (within a week) if I only need to apply the patch and 
recompile.
There are no binaries (for gcc) yet. There are OpenSolaris Operating 
System
binaries but you also need about a few days work to ensure that you can
get gcc 4.4.0 compiled on OpenSolaris (as it will not "out-of-the-box").

So I can do it correctly, for free, and very quickly --- Pick two.

If you have a patch I can get it done by next week.


> > 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.

When I rebuild and recheck I will use those options, compress the log
and mail it to you _regardless_ of it's size -- is that OK ?


You might request "FREE" daily tests of your program here: 
http://build.alchar.org/
They do this for binutils and gcc maybe they can add gdb too.

Labrat
http://build.alchar.org/cgi/showPkg?pkg=binutils_incr


Thanks,
Rob