[Qt-creator] QTCreator 4.8/ QTSDK1.2 Seggy Fault upon debug launch.

[John Carroll]

I fixed the issue. I have to run QTCreator in admin mode for windows 7. Otherwise GDB doesn't have the permissions required to function.



________________________________
 From: John Carroll <jecjackal at yahoo.com>
To: "qt-creator at qt-project.org" <qt-creator at qt-project.org> 
Sent: Thursday, March 29, 2012 10:40 PM
Subject: [Qt-creator] QTCreator 4.8/ QTSDK1.2 Seggy Fault upon debug launch.
 

Hi,

After upgrading to a new machine, I am constantly getting a segmentation fault upon launching GDB through QTCreator. The specific crash message is shown in "Seggy Fault.png". This occurs when QApplication or QCoreAppplication instances. Attached is the screen shot of the dissasembly right where the segmentation fault occur ed as well as the left pane of the debugger log. I would attach the right pane but the text was 5MB; I didn't want to bog down everyone's email. If it helps, I'd be more than happy to send it.

I'm hoping someone has a solution to this problem. Oddly enough, the first time i run QTCreator after an installation, everything works fine. However, after I close QTCreator once, I get these segmentation faults every single time I attempt to debug. I made a new GUI project and immediately tried debugging without adding any code. The segmentation fault occured and these debugger logs are from that project.

Specs:
Windows 7 x64
CPU: AMD FX-8150 (Its octal core; not sure if that could be contributing to the problem).

Thank you for your time,

Jec

_______________________________________________
Qt-creator mailing list
Qt-creator at qt-project.org
http://lists.qt-project.org/mailman/listinfo/qt-creator
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qt-creator/attachments/20120330/d7502f61/attachment.html>