When some assert() fails, gdb breaks but doesn\'t show the aborting thread. In case of a signal (like a segfault), it works fine. Is there an easy way to know what threads has just a开发者_C百科borted
I am trying to add a breakpoint in my program using b {line number} but I am always getting an error that says:
Does anyone know how to save gdb settings (like \"set print pretty on\" or \"set print elements 0\", both from here)? I don\'t want to set my 开发者_JS百科configuration every time that I will use gdb
In Windows, it is possible to set the threadname via this code. The threadname is then shown in debuggers.
I\'m trying to debug a server I wrote with gdb as it segfaults under very specific and rare conditions.
I\'m trying to debug a simple stop-and-copy garbage collector (written in C) using GDB. The GC works by handling SIGBUS. I\'ve set a breakpoint at the top of my SIGBUS signal handler. I\'ve told GDB t
I want to write a ruby program that could inspect the variable value of a program by launch the gdb and then print that value. How could I achieve this?
Why is the following code giving segmentation fault? #include <stdio.h> #include <stdlib.h>
I have some compiled libraries on x86 Linux and I want to quickly determ开发者_如何学Cine whether they were compiled with debugging symbols.The suggested command
void outputString(const char *str) { cout << \"outputString(const char *str) : \" << str << endl;
加载中,请稍侯......