Skip to content
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

gdb start two threads and the former has to be sent SIGINT(Ctrl + C) #3

Open
nevikw39 opened this issue Aug 20, 2021 · 2 comments
Open

Comments

@nevikw39
Copy link

nevikw39 commented Aug 20, 2021

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.

@mikegleasonjr
Copy link

mikegleasonjr commented May 21, 2022

@nevikw39 Did you find a solution? I am getting exactly this...

@Ascarshen
Copy link

I have the same issue here.

I am using a Mac Intel, Macos Ventura 13.5.2. gdb version 13.2.

No idea how to fix it...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants