gcc segfault: Cannot build virtualbox-ose on 8-STABLE amd64

Mario Sergio Fujikawa Ferreira lioux at FreeBSD.org
Sun Jun 6 07:45:27 UTC 2010


On 25/05/2010 05:45, Bernhard Froehlich wrote:
> On Thu, 20 May 2010 23:05:53 -0300, Mario Sergio Fujikawa Ferreira
> <lioux at FreeBSD.org>  wrote:
>> Hi,
>> 	I recently reinstalled my FreeBSD 8-STABLE box to move from
>> i386 to amd64. The hardware hasn't changed (except for an increase
>> from 4GB to 8GB ram).
>> 	There have been some hiccups and I am still trying to tidy
>> up things together.
>> 	One of the problems I am having is building virtualbox-ose
>> which previously built nicely on i386.
>> 	I am running a vanilla 8-STABLE world (no special COPTFLAGS) from May
>> 	17th.
>> $ uname -a
>> FreeBSD exxodus.fedaykin.here 8.0-STABLE FreeBSD 8.0-STABLE #2: Mon May
> 17
>> 19:53:30 BRT 2010     lioux at exxodus:/usr/obj/usr/src/sys/LIOUX  amd64
>> 	I have a clean and up to date ports tree from today.
>> All ports upgraded using portupgrade.
>> 	I am trying to build the virtualbox-ose port with vanilla cflags.
>> $ make -V CFLAGS
>> -O2 -pipe -fno-strict-aliasing
>> 	The relevant message follows:
>> ---------
>> kBuild: Installing VBoxControl =>
> /usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.8_OSE/out/freebsd.amd64/release/bin/additions/VBoxControl
>> kmk[2]: ***
> [/usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.8_OSE/out/freebsd.amd64/release/obj/VMM/tstVMStructRC.h]
>> Segmentation fault: 11 (core dumped)
>> kmk[2]: *** Deleting file
> `/usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.8_OSE/out/freebsd.amd64/release/obj/VMM/tstVMStructRC.h'
>> kmk[2]: Leaving directory
>> `/usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.8_OSE'
>> kmk[1]: *** [pass_binaries_this] Error 2
>> kmk[1]: Leaving directory
>> `/usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.8_OSE'
>> kmk: *** [pass_binaries_order] Error 2
>> *** Error code 2
>> ---------
>> 	The complete build log can be found at
>> http://people.freebsd.org/~lioux/virtualbox/2010051900/emulators__virtualbox-ose_3.1.8_build.log.bz2
>> 	My virtualbox-ose work directory can be found at
>> (you need archivers/xz to extract it)
>> http://people.freebsd.org/~lioux/virtualbox/2010051900/emulators__virtualbox-ose__work.tar.xz
>> 	Let me know if there is anything I can do to help.
>> 	Regards,
>> ps: virtualbox-ose-kmod builds without a problem as well as my other
>> 1482 ports. :)
> Segmentation fault: 11 comes from gcc so this is likely to be a compiler
> bug and i'm not sure if we can help in this case so I cc'd current at . Could
> you try to get a backtrace from the core file that it has dumped?

   The only core file I could find was tstVMStructRC.core. The backtrace 


$ script gdb.log gdb 

Script started on Sun Jun  6 01:13:16 2010
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 
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"...
Core was generated by `tstVMStructRC'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/lib32/libc.so.7...done.
Loaded symbols for /usr/lib32/libc.so.7
Reading symbols from /libexec/ld-elf.so.1...done.
Loaded symbols for /libexec/ld-elf.so.1
#0  0x0805099c in _start ()
(gdb) bt
#0  0x0805099c in _start ()
#1  0x00000001 in ?? ()
(gdb) quit

Script done on Sun Jun  6 01:13:21 2010


   I've done another round of portupgrade(s) and tried rebuilding 
virtualbox-ose again to no vail.

$ uname -a
FreeBSD exxodus.fedaykin.here 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #6: 
Thu Jun  3 20:30:23 BRT 2010 
lioux at exxodus:/usr/obj/usr/src/sys/LIOUX  amd64

   On a side note, this might be a coincidence but I haven't been able 
to build virtualbox since the xorg update to 7.5 AND since my switch 
from 8-STABLE i386 TO amd64. Both happened around the same week. I have 
no idea which one is to blame.

   I did a clean amd64 install though, not an inplace upgrade.

   The latest build log can be found at:


   The port work directory of the failed build can be found at:


   Let me know if there is anything I can try:

	Mario Ferreira

Mario S F Ferreira - DF - Brazil - "I guess this is a signature."
feature, n: a documented bug | bug, n: an undocumented feature

More information about the freebsd-current mailing list