Gdb debugging multithreading question Gdb debugging multi-threaded, multi thread switching back and forth between the sponsors, but also from the implementation of threads LINUX restrictions thread debugging activities, the non-implementation activities threads are free, clog housed in single-step implementation. Opition:set scheluer-locking on/off/step inside that can be used to help to set up a thread lock, but after I set up, the thread does not help if there said, will be first in a number of switching between the threads, thread implementation is still separately. not all non-blocking activities thread, how is this thing? Pay close attention No tests were set scheduler-locking help landlord about the top. Brother months related issues. Gcc compiler I use more than one programming (NPTL), the operation of the deadlock caused a.out course, I have spent a core file and kill orders to kill. But when I used gdb debugging a.out core of the core file, the [threads can summarize the thread is running, but besides the main thread, a thread can not implement any backtrace that address 0x0. Is there any solution? [ Closed window ]