-
-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash when running CoreFoundation applications (and wqthread-related problems) #4
Comments
@Qix-, thanks for your report! The Without a program to test, it will be extremely tricky for me to debug. As As this is a really similar case to the |
I actually managed to reproduce the problem fairly easily, running valgrind with Hex Fiend (I am guessing any I have good and bad news: I already have a fix which I recovered from an old patch (you can try it here), however you will probably run into another problem rightaway: SIGSEGV on I also have a fix for that issue, but it is really experimental (see here) and need polishing. |
Yep definitely using CoreFoundation (it's a game engine, with a bunch of window calls). Glad it wasn't localized to my application ^^ As for testing the patches, should I rebase one onto the other in order to test both, or does the last link include them both? And should I build via the makefiles or is there a fancy |
I just merged Unfortunately, I am not aware of any brew command that does that, you will need to build via the Makefile. |
Output from
If you'd like, I can do a run with the high-verbosity flags you mentioned before. |
No it's alright, I get the exact same error, so at least there is comfort in that... I'll need to continue working on the wqthread fix as it's obviously still buggy. |
Alright, sounds good :) Let me know if I can help in any way! Thanks for all of the work you've done, it's incredibly appreciated. |
Thanks a lot for your kind words! I will try to look into it, but if you want to investigate yourself, it would be greatly appreciated. |
I'm not sure If this is the right place to ask this, is there any tool that can be used to detect memory leak beside valgrind? Because of wqthread issues it's impossible to check multithread app with valgrind in osx according to this https://bugs.kde.org/show_bug.cgi?id=380269 which might be related, link is already 4 years old and I guess it's safe to assume it would not be fixed shortly |
I'm trying really hard to debug this but getting nowhere, even with
lldb
,vgdb
andvalgrind --vgdb=yes
.The new valgrind patch for MacOS mojave results in a successful install but on a few non-trivial applications Memcheck is causing a
SIGILL
to be raised. The application in question runs fine, otherwise.Here is the stack:
The only other output comes before the application even starts - I don't know if it's relevant or not:
I'm having issues creating a minimal reproduction case, as I have no idea which part of the application is causing this to happen (since the stacktrace doesn't give me any application-specific information).
Any tips on how to debug this would be appreciated :)
The text was updated successfully, but these errors were encountered: