Follow-up Comment #5, bug #25040 (project gnustep):
> 0x8 doesn't look like a pointer, it seems to be a value
> and 0 is something of an unlikely length.
I agree ... the length comes from the ffi stuff so it does suggest a problem
in libffi.
I also wonder how/why the crash occurred though ... with a length of zero the
memcpy should have done nothing, so there should be no reason for it to
segfault ... so perhaps the data in the stacktrace is corrupt and we aren't
seeing the values that were really used.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?25040>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnustep
