Revision: 5837
          http://ipcop.svn.sourceforge.net/ipcop/?rev=5837&view=rev
Author:   gespinasse
Date:     2011-09-07 06:45:08 +0000 (Wed, 07 Sep 2011)
Log Message:
-----------
Upgrade gdb to 7.3.
This fix the test suite on more recent distrib (for example switching from 
debian v5 lenny to v6 squeeze)
for reason I haven't identified. Without upgrade, test log is full of ERROR: 
Couldn't send <> to GDB

Core dump feature usage for gdb test suite need that you unplug pipe to apport 
that most distrib have set.
Look in lfs/gdb if you are curious for an example how to do that.

Modified Paths:
--------------
    ipcop/trunk/lfs/gdb

Modified: ipcop/trunk/lfs/gdb
===================================================================
--- ipcop/trunk/lfs/gdb 2011-09-03 11:06:21 UTC (rev 5836)
+++ ipcop/trunk/lfs/gdb 2011-09-07 06:45:08 UTC (rev 5837)
@@ -33,7 +33,7 @@
 include Config
 
 PKG_NAME   = gdb
-VER        = 7.2
+VER        = 7.3
 HOST_ARCH  = all
 OTHER_SRC  = yes
 
@@ -55,7 +55,7 @@
 
 $(DL_FILE)                        = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_MD5                    = 64260e6c56979ee750a01055f16091a5
+$(DL_FILE)_MD5                    = 485022b8df7ba2221f217e128f479fe7
 
 install : $(TARGET)
 
@@ -125,12 +125,23 @@
                                -e 's/gdb\.pascal //' -e 's/gdb\.python //' \
                                gdb/testsuite/Makefile
        cd $(DIR_APP) && rm -rf 
gdb/testsuite/gdb.{ada,fortran,java,objc,pascal,python}
+       # Some tests need gcc-4.5 features at least and will fail with gcc-4.4
+       # like cc1: error: unrecognized command line option "-fsplit-stack"
 
-       # gdb.base/auxv.exp require -c unlimited
+       # I try to avoid test timeout, I had some with laptop Intel Celeron CPU 
540 @ 1.86GHz
+       # First, create site.exp, then we could add a timout value there
+       cd $(DIR_APP)/gdb/testsuite && make site.exp
+       # Some timeout still remain, even with 120 or 240 value
+       cd $(DIR_APP)/gdb/testsuite && echo 'set gdb_test_timeout 60' >>site.exp
+       # Some tests require core dump usage (ulimit -c unlimited)
+       # If apport is plugged to /proc/sys/kernel/core_pattern, gdb will fail 
to find the core dump.
+       # In that case, you may want switch to root and echo "core.%e.%p" > 
/proc/sys/kernel/core_pattern
+       # and restore pipe to apport after the tests
        -cd $(DIR_APP) && \
                bash -c 'ulimit -c unlimited; \
                        make -j 1 -k check ' &> 
$(DIR_TEST)/$(THISAPP)-$(STAGE_ORDER).log
-       # Should have less than 40 failures, philosopher error randomly vary 
(from machine to machine?)
+       # Should have approximately 41 failures with core dump working,
+       # philosopher error randomly vary (from machine to machine?)
 
        # restore gcc default hardened behavior
        rm `dirname $$(gcc --print-libgcc-file-name)`/specs

This was sent by the SourceForge.net collaborative development platform, the 
world's largest Open Source development site.


------------------------------------------------------------------------------
Using storage to extend the benefits of virtualization and iSCSI
Virtualization increases hardware utilization and delivers a new level of
agility. Learn what those decisions are and how to modernize your storage 
and backup environments for virtualization.
http://www.accelacomm.com/jaw/sfnl/114/51434361/
_______________________________________________
Ipcop-svn mailing list
Ipcop-svn@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ipcop-svn

Reply via email to