On 64-bit arches sizeof(int) is 4, sizeof(void*) is 8, so if that
function was expecting a 64-bit value, it used to get half of that full
of garbage. On 32-bit arches sizeof(int) == sizeof(void*), so you
wouldn't see anything.
But this should only come up when you're calling an undeclared function,
and the compiler no idea what the function expects. Do you see any
compiler warnings about implicit function declarations when you build
with -Wall?
Also, the segfault that I saw happened on a 32-bit system, so it must be
a different issue. Mine appears to be fixed: I can run
mgp /usr/share/doc/mgp/examples/tutorial.mgp
on Maverick with no issues.
--
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for Debian.
https://bugs.launchpad.net/bugs/63976
Title:
[edgy] mgp segfaults on startup
_______________________________________________
Mailing list: https://launchpad.net/~registry
Post to : registry@lists.launchpad.net
Unsubscribe : https://launchpad.net/~registry
More help : https://help.launchpad.net/ListHelp
