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
Too many thanks for you for the patched version of gdb, finally I can use gdb on my MacBook.
But when I press r and start debugging, gdb first printed something like [New Thread 0x2c03 of process 50666] and do no response until I press Ctrl + C to stop the thread, and then it printed [New Thread 0x5303 of process 50666] warning: unhandled dyld version (17) so that my program just started inputting and outputting.
I've googled unhandled dyld version, but I still have no idea.
I'm wondering whether gdb should work like this. It makes a bit inconvenience.
Hello,
Too many thanks for you for the patched version of gdb, finally I can use gdb on my MacBook.
But when I press r and start debugging, gdb first printed something like
[New Thread 0x2c03 of process 50666]
and do no response until I press Ctrl + C to stop the thread, and then it printed[New Thread 0x5303 of process 50666] warning: unhandled dyld version (17)
so that my program just started inputting and outputting.I've googled unhandled dyld version, but I still have no idea.
I'm wondering whether gdb should work like this. It makes a bit inconvenience.
PS: gdb was codesigned, SIP partially disabled, DevToolsSecurity enabled, startup-with-shell off.
The text was updated successfully, but these errors were encountered: