Problems with threads and windows

**SkripT** · 13th January 2006, 18:32

Sorry for my ignorance but could you please tell me how to run the debugger in the commad line to obtain the backtrace? Thanks

**jacek** · 13th January 2006, 19:28

Originally Posted by SkripT

how to run the debugger in the commad line to obtain the backtrace?

If you use MinGW, it should be:

shell Code:

Switch view

C:\...> gdb prog.exe
(gdb) run
<program crashes>
(gdb) bt
<backtrace>
(gdb) quit

C:\...> gdb prog.exe
(gdb) run
<program crashes>
(gdb) bt
<backtrace>
(gdb) quit

To copy to clipboard, switch view to plain text mode

**SkripT** · 13th January 2006, 19:34

thanks a lot i'm going to try it.

**SkripT** · 14th January 2006, 00:51

Hi, here's the backtrace as a result of a program crash:

Program received signal SIGSEGV, Segmentation fault.
[Switching to thread -277..........]
0x1012c44b in _size_of_stack_reserve__ ()

and the message from the program drwatson of windows is that the program has made an illegal acess to memory.
As I think, crashes as a result of an overload of the stack. I guess that's because I am working with some QImages at the same time and I think that could be better to define the images in dynamic memory. I will try it.

**jacek** · 14th January 2006, 00:57

Originally Posted by SkripT

Hi, here's the backtrace as a result of a program crash

It's rather short. Wasn't there more output?

As I think, crashes as a result of an overload of the stack. I guess that's because I am working with some QImages at the same time and I think that could be better to define the images in dynamic memory.

AFAIK QImage stores data on the heap.

**SkripT** · 16th January 2006, 11:07

Hi again, gdb alerts me with two warnings that I tried to re-register class QString because I was trying to do a qregistertyper of QString. I have deleted the instruction and seems that the program not crashes, in the short time that I have tested it. Could I think that this was the problem?

**jacek** · 16th January 2006, 18:16

Originally Posted by SkripT

Hi again, gdb alerts me with two warnings that I tried to re-register class QString because I was trying to do a qregistertyper of QString.

That warning comes from Qt itself. If you add "CONFIG += console" to your .pro file, you should be able to see such warnings on the console, without the need of debugger.

Originally Posted by SkripT

I have deleted the instruction and seems that the program not crashes, in the short time that I have tested it. Could I think that this was the problem?

Might be, but it shouldn't crash just because you tried to register something twice.

**SkripT** · 16th January 2006, 18:46

Ok jacek, thanks for tell me how to view the warnings from the console and for all the other suggestions. I will test the program a little more running it with the debugger, hoping that doesn't crash