You are not logged in.

Dear visitor, welcome to QtForum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

1

Sunday, September 19th 2010, 7:59pm

Segmentation fault when trying to debug

Whenever I try to debug in QT Creator (even samples, like "animatedtiles") I get the following error message as soon as I press F5:

Source code

1
2
3
The inferior stopped because it received a signal from the Operating System.
Signal name : SIGSEGV
Signal meaning : Segmentation fault


The application output window shows the following text at the same time:

Source code

1
2
3
4
(Internal error: pc 0xf in read in psymtab, but not in symtab.)
(Internal error: pc 0xf in read in psymtab, but not in symtab.)
(Internal error: pc 0xf in read in psymtab, but not in symtab.)
(Internal error: pc 0x0 in read in psymtab, but not in symtab.)


I have attached the wxvault.txt with the dissasembler code being executed (the last line is where the segmentation fault happens). The problem is the same for all projects. I'm using Windows XP SP3 with Qt Creator 2.0.1 based on Qt 4.7.0 (32 bit), revision 113d4c5618.

What is wrong?

Regards,
Alex
alexrixhardson has attached the following file:
  • wxvault.txt (112.66 kB - 35 times downloaded - latest: Nov 21st 2011, 7:50am)

2

Saturday, November 27th 2010, 2:50am

I am having the exact same problem as Alex.
Except the application output window shows no output.

I am also using Windows XP SP 3.
Qt Creator 2.0.1 Based on Qt 4.7.0 (32 bit)
Built on Aug 24 2010 at 11:00:55
From revision 97d831e3de
(Note, slightly different revision of Qt Creator than Alex reported.)

3

Saturday, November 27th 2010, 3:28am

Update:

This is definitely being caused by my COMODO firewall software.

I had suspected this right off, so I had stopped COMODO and rebooted, so thinking I'd removed that possibility. It seems some part of COMODO is still running. Also, choosing to disable firewall security and defense security still did not help. Possibly other firewall software does something similar. Haven't figured out how override this in COMODO. I told COMODO the debugger was a trusted app, then tried making it an installer even, gave it every permission possible, etc., etc...seems COMODO just stops it anyway).

Will post back if I figure it out, but for those searching and arriving at this thread when having this problem, you should definitely check if your firewall is causing the seg fault. You can easily check by looking at what file is at level 0 when the seg fault happens. If it is a DLL associated with your firewall....well, bingo.

4

Monday, July 25th 2011, 9:38am

Hi guys, I had the same problem and found that it is possible to setup comodo to work with my qt4 project.
You should do the following steps:
1) Open Comodo
2) Go to Defense+ tab
3) Open Defense+ Settings
4) Go to Execution Control Settings
5) Press Exception button
6) Add Qt4, mingw(if any) and Your project root directories.

That's all.

5

Saturday, November 19th 2011, 12:14pm

I have the same problem, but do not use COMODO.

The program runs normally on another machine I have which is Win7 x32b. On the Win7 x64b, however, it fails at runtime (Segmentation Fault) with the following error line appearing a number of times:

(Internal error: pc 0xf in read in psymtab, but not in symtab.)

In Release mode, the program fails to run and exits with code -1073741819

I am first asking for help on understanding the error I am facing here. If necessary, I'll then post my code. Note that, when using the x64b machine, I am still compiling a 32b application (using the default install lib of Qt, etc.).

Thanks.

This post has been edited 1 times, last edit by "estebal" (Nov 19th 2011, 12:22pm)