Date: Thu, 26 Jun 2008 16:10:10 GMT From: Chris Bowlby <excalibur@accesswave.ca> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/124353: cvsup(1): CVSup coredumps with Bus Error since installworld of 6.3-STABLE on 28/5/08 [regression] Message-ID: <200806261610.m5QGAAiE058398@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/124353; it has been noted by GNATS. From: Chris Bowlby <excalibur@accesswave.ca> To: bug-followup@FreeBSD.org, srp@zzap.org Cc: Subject: Re: bin/124353: cvsup(1): CVSup coredumps with Bus Error since installworld of 6.3-STABLE on 28/5/08 [regression] Date: Thu, 26 Jun 2008 12:38:11 -0300 Hi Guys, I am also running into this particular issue, and the hardware I am running on is very similar to the one Simon is running, except I am running on a generic kernel, not a customized one as of yet. Here is what I have done so far: 1. I have recompiled cvsup and all the dependancy packages that it uses. 2. I have run a back-trace of the cvsup package, but I do not seem to have debugging symbols installed (never needed to before so I am unsure how to do that). Here is the output: amaethon# gdb `which cvsup` GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"...(no debugging symbols found)... (gdb) set arg -L 2 -g /root/src (gdb) run Starting program: /usr/local/bin/cvsup -L 2 -g /root/src (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...Parsing supfile "/root/src" Connecting to cvsup5.FreeBSD.org Connected to cvsup5.FreeBSD.org Server software version: SNAP_16_1h Negotiating file attribute support Exchanging collection information Establishing multiplexed-mode data connection Running Program received signal SIGBUS, Bus error. 0x0000000800966d3f in fcntl () from /lib/libc.so.6 (gdb) bt #0 0x0000000800966d3f in fcntl () from /lib/libc.so.6 #1 0x000000000046550b in fnmatch () #2 0x0000000000474430 in fnmatch () #3 0x0000000000474215 in fnmatch () #4 0x000000000046f5a7 in fnmatch () #5 0x000000000042e0d7 in ?? () #6 0x000000000042db5c in ?? () #7 0x000000000041cc2e in ?? () #8 0x0000000000415bcd in ?? () #9 0x000000000041525f in ?? () #10 0x0000000000414d3a in ?? () #11 0x000000000049f840 in calloc () #12 0x000000000048fb11 in fnmatch () #13 0x00007fffffffd5f8 in ?? () #14 0x00007fffffffeb60 in ?? () #15 0x00007fffffffec28 in ?? () #16 0x0000000000000000 in ?? () #17 0x0000000000000000 in ?? () #18 0x0000000000000000 in ?? () #19 0x000000000000037f in ?? () #20 0x0000000000000000 in ?? () #21 0x00000000006476c0 in ?? () #22 0x00000000006476c0 in ?? () #23 0x0000000000494e5d in fnmatch () Previous frame inner to this frame (corrupt stack?) If someone can let me know on the quick way to enable debugging symbols, I'll re-compile it and re-run the back-trace for you.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200806261610.m5QGAAiE058398>