On 08/07/11 19:15, Basile Starynkevitch wrote:
On Fri, Jul 08, 2011 at 06:41:30PM +1000, Allan McRae wrote:
empty-file-for-melt.c
cc1: note: MELT is bootstrapping so ignore builtin source directory
/usr/lib/gcc/i686-pc-linux-gnu/4.6.1/plugin/melt-source and module
directory
/usr/lib/gcc/i686-pc-linux-gnu/4.6.1/plugin/libexec/melt-modules
*** WARNING *** there are active plugins, do not report this as a
bug unless you can reproduce it without enabling any plugins.
Event | Plugins
PLUGIN_FINISH_UNIT | melt
PLUGIN_FINISH | melt
PLUGIN_GGC_START | melt
PLUGIN_GGC_MARKING | melt
PLUGIN_ATTRIBUTES | melt
PLUGIN_START_UNIT | melt
PLUGIN_PRAGMAS | melt
cc1: internal compiler error: Segmentation fault
Please submit a full bug report,
Did you install a previous release of MELT plugin (e.g. 0.8rc1 or 0.7)? If
you did, you have to remove it entirely (eg remove all files named *melt*)?
I have no previous MELT plugins installed.
What further information do you require for this?
Perhaps a gdb backtrace of the crash?
Maybe not that helpful given things have been stripped... I can rebuild
without stripping if helpful.
#0 0xf7fe6941 in _dl_lookup_symbol_x () from /lib/ld-linux.so.2
#1 0xf788ed60 in ?? () from /lib/libc.so.6
#2 0xf788f1e7 in _dl_sym () from /lib/libc.so.6
#3 0xf7902d66 in ?? () from /lib/libdl.so.2
#4 0xf7feb66f in _dl_catch_error () from /lib/ld-linux.so.2
#5 0xf790333a in ?? () from /lib/libdl.so.2
#6 0xf7902de4 in dlsym () from /lib/libdl.so.2
#7 0xf71a7605 in melt_dlsym_all () from ./melt.so
#8 0xf71a7666 in melt_dynobjstruct_fieldoffset_at () from ./melt.so
#9 0xf708ad3c in warmelt_first_initialmeltchunk_19 ()
from melt-stage0-dynamic/warmelt-first-0.so
#10 0xf70fa485 in start_module_melt ()
from melt-stage0-dynamic/warmelt-first-0.so
#11 0xf71b9b3b in meltgc_make_load_melt_module () from ./melt.so
#12 0xf71c3bc3 in plugin_init () from ./melt.so
#13 0x082d5565 in ?? ()
#14 0x087663c5 in htab_traverse_noresize ()
#15 0x082d5ebd in initialize_plugins ()
#16 0x08364c2e in toplev_main ()
#17 0x080d645b in main ()
Note that this only happens for me on i686. I have just set off a build
on my x86_64 system (toolchain build with exactly the same
configuration) and I do not run into this issue.
Allan