#38 ICE: segmentation fault


For quite a while there has been a problem compiling a file in the MAME/MESS source code:

Compiling src/mame/drivers/megadriv.c...
src/mame/drivers/megadriv.c: In function 'void driver_init__32x(running_machine*)':
src/mame/drivers/megadriv.c:6577: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
make: *** [obj/windows/mess/mame/drivers/megadriv.o] Error 1

Unfortunately it's not always reproducible and I never saw it myself, but several people around the globe experienced it. It it being discussed on the MESS forum: http://www.bannister.org/forums/ubbthreads.php?ubb=showflat&Number=62342&page=1

You can get the latest MAME source from http://mamedev.org and need to update it to 0.138u1 or get the latest MESS source from SVN, which includes MAME (see http://mess.redump.net/subversion\).

The isolated command-line to compile this files appears to be:

gcc -DCRLF=3 -DINLINE="static inline" -DLSB_FIRST -DNDEBUG -DX64_WINDOWS_ABI -DUNICODE -D_UNICODE -Dmain=utf8_main -DMESS -DWINVER=0x0400 -D_WIN32_IE=0x0501 -DDECL_SPEC= -DZEXTERN=extern -DNATIVE_DRC=drcbe_x86_be_interface -pipe -O3 -Werror -fno-strict-aliasing -Wall -Wcast-align -Wundef -Wformat-security -Wwrite-strings -Wno-sign-compare -Isrc/mess -Iobj/windows/mess/mess/layout -Isrc/emu -Iobj/windows/mess/emu -Iobj/windows/mess/emu/layout -Isrc/lib/util -Isrc/osd -Isrc/osd/windows -Isrc/lib/expat -Isrc/lib/zlib -include src/osd/windows/winprefix.h -DDIRECTINPUT_VERSION=0x0700 -x c++ -std=gnu++98 -Isrc/mame -Isrc/mess/osd -Isrc/mess/osd/windows -Isrc/mess/tools -Isrc/mess/tools/imgtool -Isrc/mess/tools/castool -Isrc/osd/winui -Isrc/mess/osd/winui -c src/mame/drivers/megadriv.c -o obj/windows/mess/mame/drivers/megadriv.o

I am still trying to get preprocessed files and a gdb backtrace from a crash situation.


  • Oliver Stöneberg

    Sorry, I forgot to mention the version of the compiler:

    Using built-in specs.
    Target: i686-w64-mingw32
    Configured with: ../gcc44-svn/configure --target=i686-w64-mingw32 --host=i686-w64-mingw32 --disable-multilib --disable-nls --prefix=/mingw64-w32 --with-sysroot=/mingw64-w32 --with-gmp=/mingw64-w32 --with-mpfr=/mingw64-w32 --enable-languages=c,c++
    Thread model: win32
    gcc version 4.4.3 20091223 (prerelease) r155431 (GCC)

  • Oliver Stöneberg

    I got the command-line from a crash:

    gcc -DCRLF=3 -DINLINE="static inline" -DLSB_FIRST -DNDEBUG -DX64_WINDOWS_ABI -DUNICODE -D_UNICODE -Dmain=utf8_main -DNATIVE_DRC=drcbe_x86_be_interface -pipe -O3 -Werror -fno-strict-aliasing -Wall -Wcast-align -Wundef -Wformat-security -Wwrite-strings -Wno-sign-compare -Isrc/mame -Iobj/windows/mame/mame/layout -Isrc/emu -Iobj/windows/mame/emu -Iobj/windows/mame/emu/layout -Isrc/lib/util -Isrc/osd -Isrc/osd/windows -Isrc/lib/expat -Isrc/lib/zlib -include src/osd/windows/winprefix.h -DDIRECTINPUT_VERSION=0x0700 -x c++ -std=gnu++98 -c src/mame/drivers/megadriv.c -o obj/windows/mame/mame/drivers/megadriv.o

    Unfortunately the crash is not experienced by just using the command-line, but just my running the whole make process. Even adding CC=gcc to show the gcc call is causing the crash to disappear. There are also no preprocessed files created when the crash appears.

  • Ozkan Sezer

    Ozkan Sezer - 2010-06-01

    That build looks like one of my ones and the compiler version is rather old. Is the ice reproducible with new builds?

  • Oliver Stöneberg

    It's yours and it's the MAME approved toolchain so we have to deal with it.

    Fortunately we got a reproducible case right now and I suggested to the user, that he is trying a newer build. I will keep you posted.

  • Kai Tietz

    Kai Tietz - 2010-07-10
    • status: open --> pending-remind
  • Kai Tietz

    Kai Tietz - 2010-07-10

    Did the new build worked for your user?

    I tried to reproduce it, and didn't got this ICE anymore.

  • SourceForge Robot

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).

  • SourceForge Robot

    • status: pending-remind --> closed-remind
  • NightStrike

    NightStrike - 2010-07-25
    • status: closed-remind --> closed-works-for-me
  • NightStrike

    NightStrike - 2010-11-16
    • labels: --> Build 3rd party app

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks