You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Receive a segfault when running elkhound/elkhound elkhound/examples/crash1.gr on Mac OS X. Have built the tools using Apple LLVM version 8.0.0 (clang-800.0.38). Debegging segfault reveals the cause to be dereferencing a null pointer when calling LocString::<< operator (loc.str is NULL). From the comments in ast/locstr.h I see that the loc.str is permitted to be NULL:
// experimenting with allowing 'str' to be null, which is convenient
// when the string table isn't available
In that case, the << operators should deal gracefully with str==NULL.
The text was updated successfully, but these errors were encountered:
sam-ellis
added a commit
to sam-ellis/oink-stack
that referenced
this issue
Oct 15, 2016
Fix for issue dsw#18. As per the comments in locstr.h the str field is permitted to be NULL. This fix protects against NULL pointer dereference in the << operators. This allows elkhound/elkhound elkhound/examples/crash1.gr to pass (not segfault) on Mac OS X.
Receive a segfault when running elkhound/elkhound elkhound/examples/crash1.gr on Mac OS X. Have built the tools using Apple LLVM version 8.0.0 (clang-800.0.38). Debegging segfault reveals the cause to be dereferencing a null pointer when calling LocString::<< operator (loc.str is NULL). From the comments in ast/locstr.h I see that the loc.str is permitted to be NULL:
In that case, the << operators should deal gracefully with str==NULL.
The text was updated successfully, but these errors were encountered: