The program is working fine when I put a breakpoint, then a partition fault occurs. Is this me or GDB? This is never happening at run time and if I instantiate only one object then there is no problem.
Using QTrue on ubuntu x86_64 Carmela Koala
UPDATE1:
I have created a small program with a simplified version of that class you can download it:
Just put a breakpoint on the first line of the function calling the draft chart () and step up to be the default font
UPDATE2: This is another small program, but it is practically a Mandelbrot example Is similar and it is still happening. You can separate it from the Mainlbrot so that you can see the small difference.
To answer your question: Yes, you have to debug many Should be able to use threads using GDB depends on the sound to be dependent on concurrent design.
There is a chance that you have a race condition that has access to your threads. It is possible that this problem is not seen when you run the program normally, but adding the debugger changes time and scheduling, even when you are segfault, you should be able to use the debugger to break. Understanding where this happens, you can tell about race conditions or corruption, whatever the case.
It is worth seeing because even in most 'run time' circumstances it may not happen, different systems appear under load conditions.
Comments
Post a Comment