Not for a moment. All my spare time is devoted to gcc, OpenSolaris and a few other things ...Did you consider fixing this, and posting a patch at gdb-patches@ ?
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. :) .
I like to see the "# of unexpected failures" closer to zero.Someone has to put effort into making that happen.
Yes, it would be nice.
If you look at the log file, does it look like many failures are ...
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. Thanks for accepting my report, Rob -----Original Message----- From: Pedro Alves <pe...@codesourcery.com> To: bug-gdb@gnu.org Cc: rob1w...@aol.com Sent: Fri, 16 Jan 2009 6:39 amSubject: 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 Thursday 15 January 2009 13:20:55, rob1w...@aol.com wrote:
While building I found one "-Werror":
cc1: warnings being treated as errors ../../gdb-cvs/gdb/procfs.c: In function 'proc_set_watchpoint':../../gdb-cvs/gdb/procfs.c:2942: error: dereferencing pointer
'pwatch'
does break strict-aliasing rules
Nasty. Even more, the current code assumes that alignof (arg.watch) == alignof (prwatch_t)). Did you consider fixing this, and posting a patch at gdb-patches@ ? [...] If you look at the log file, does it look like many failures arerelated to \r\n patterns being misdetected? Passing --debug to RUNTESTFLAGS
will make it easier to spot. I had some troubles related to that when I last ran the testsuite on that version of Solaris. See here: http://sourceware.org/ml/gdb/2008-08/msg00144.html I still don't know what the proper fix is.
I like to see the "# of unexpected failures" closer to zero.
Someone has to put effort into making that happen. -- Pedro Alves
gdb_check_log.txt.gz
Description: GNU Zip compressed data
_______________________________________________ bug-gdb mailing list bug-gdb@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gdb