Yosemite compatibility?

Question

Yosemite compatibility?

ni4 opened this issue 10 years ago · 9 comments

Hi. I tried mach_inject + some Finder integration code on Mac OS X 10.10 Yosemite (Beta6) - and it fails in injected thread, on the first fopen/freopen/fwrite function call.
Everything works fine on Mavericks.

Anyone more experienced tried to run mach_inject on Yosemite? Or, somebody can recommend a way to debug this issue?
Thanks, all input is appreciated.

Answer 1 · 2014-09-03T15:11:22.000Z

Hello,

I have the same issue, do you have the following error??

com.apple.xpc.launchd1: Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.ReportCrash
Sep 3 17:03:33 iMac-de-admin com.apple.xpc.launchd1: Service exited due to signal: Segmentation fault: 11

Applications which use this, like dropbox is not working.

do you find a way to fix or debut that ??

Thanks,

Answer 2 · 2014-09-09T15:15:28.000Z

I have just a segmentation fault in inject code, but most likely it's the same problem as yours.
Unfortunately, do not have a way to fix it at the moment - focused on other tasks.

Answer 3 · 2014-09-16T22:28:26.000Z

Try removing the fprintf debugging code from INJECT_ENTRY in mach_inject_bundle_stub.c. It's ultimately trying to take out a pthread lock, but it's not safe to do so until we are inside pthread_entry

Answer 4 · 2014-09-17T08:11:17.000Z

It's working back to normal !!!!

Thanks

Answer 5 · 2014-09-19T08:26:07.000Z

Thank you very much, it worked.
And it seems that without this modifications it was failing sometimes on 10.9, or am I wrong with this?
And, btw, why it worked on 10.9 and stopped to work at 10.10, any ideas?

Answer 6 · 2014-10-03T19:44:06.000Z

Removing fprintf from INJECT_ENTRY fixed the problem for me as well. I'm not sure I understand what pthread lock it was trying to take out? Can you explain? Thanks @iccir

Answer 7 · 2014-10-04T00:39:15.000Z

Effectively, when we are in INJECT_ENTRY, we are in a very hostile environment and limited in what we can call. We have no idea what the state of the rest of the app is, and are limited to calling async-safe APIs.

See Landon Fuller's excellent article for more information about this: http://landonf.bikemonkey.org/code/objc/Reliable_Crash_Reporting.20110912.html

I can't remember the exact backtrace in the crash log, but fprintf() was calling into other functions which eventually tried to take out a lock, and hit an assertion in the pthread code.

Answer 8 · 2014-10-15T09:31:40.000Z

It was fixed(hopefully) in #14
Should we close this issue?

Answer 9 · 2014-10-17T08:55:11.000Z

Yes, I think it can be closed now.