When I type gdb a.out
and then run
inside the gdb itself I get stuck on the empty line:
jericho-laptop:exploit.education jericho$ gdb a.out
GNU gdb (GDB) 9.1
...
Reading symbols from a.out...
(No debugging symbols found in a.out)
(gdb) run
Starting program: /Users/jericho/Desktop/exploit.education/a.out
[New Thread 0x2703 of process 53514]
[New Thread 0x2603 of process 53514]
<<< STUCK IN HERE >>>
It obviously says 2 threads of a process 53514 were created. Though the program is not multi-threaded it is a simple tiny C crackme with only a main function.
The console gets stuck, I can type whatever I want but I can't get it to continue and I can't get it to quit. I have to forcibly close the terminal window.
What am I doing wrong?
I don't know what to do. The GDB does the same for any other binary I try to run. I am using MacOS with gdb 9.1 which I codesigned.
gdb
developers sourceware.org/bugzilla/show_bug.cgi?id=24069 – honey_badger Apr 13 '20 at 21:43