[Vm-dev] another GCC issue?

Igor Stasenko siguctua at gmail.com
Wed Mar 28 12:43:08 UTC 2012

or perhaps not..
i am trying to build the cog cocoa VMs using configs made by Esteban..

CogCocoaIOSConfig new
"	generateForDebug;"
	addExternalPlugins: #( FT2Plugin  );
	addInternalPlugins: #( UnixOSProcessPlugin );
	generateSources; generate.

it is not a functional bug.. because if i use #generateForDebug,
everything works fine (but slow ;)
but if i do #genearateForRelease, VM crashes with following:

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x5eedca7a
0x0000dfb6 in concretizeAt ()
(gdb) bt
#0  0x0000dfb6 in concretizeAt ()
#1  0x00014996 in generateInstructionsAt ()
#2  0x000000c9 in ?? ()

i am not sure how to squeeze more info about this crash point..
because stack trace is cut by gdb,
which /.another rant here./ stupidly stops scanning stack frames once
it discovers a frame which code is outside of memory covered by debug

Ah.. yes.. and addition info.. the difference between generateForDebug
and generateForRelease



Best regards,
Igor Stasenko.

More information about the Vm-dev mailing list