Segmentation fault QtCreator 3.1.1

clochydd

Usually, when a segmentation fault appears in Creator/debug mode, the program is stopped and you will see the line where the execution failed.
Do you mean that the Creator stops immediately after start without even trying to execute your app?

deleted28

the only way to get any message is to start creator from terminal.
After the crash, creator entirely disappears and only the segfault
message is visible in the terminal.
Maybe i should start creator with debugger, but i do not know how to.

And, when creator crashes after run application, the app remains running,
"only" the IDE disappears.

clochydd

What message do you see when starting in terminal? KF5?
Do you know "this blog: ":http://blog.martin-graesslin.com/blog/tag/kf5/

deleted28

i get only "segmantation fault" no message about "kf5"
I checked package manager and i do not find any kf5 stuff.

I found some issue reports here:
"kf5 mentioned":https://bugs.archlinux.org/task/40493
Maybe this has nothing to do with my problem.

And this crash appears since few days. All the time before
QtCreator worked perfect. Anyway, package manager suggests
update and i mostly install it.

No, i did not know this KF5 Blog and i still do not know what it is.

clochydd

But why did you mention kf5 (=KDE Framework 5) in your first post? Any message related to that?
Did you update the Creator? AFAIK the 3.1.1 belongs to Qt 5.3.
As the first step, I would now start the Creator, open a simple app from the examples, build and start in debug mode.

deleted28

I mentioned kf5 because i found a similar problem on the web
which was able to solve by removing kf5 packages.
As a possible hint only, nothing more.
I installed from onlineinstaller and updated all to 5.3.0-1
which contains QtCreator 3.1.1 (Opensource), Based on Qt 5.2.1 (GCC 4.6.1, 32 bit).
I do not really understand why it should make sense to start in debugmode when the entire IDE disappears and no more outputs
are available.

clochydd

Why start in debug:
If starting in a terminal window does not produce any message, setting a breakpoint in the first row of your app and starting in debug by pressing F5 could help to locate the fault.
It would not help, if your Creator is crashed.

deleted28

bq. It would not help, if your Creator is crashed.

agree

I will try several more or less crazy things now. If i get any info what is going on, i 'll be back here. Thank you so far :)

I remember there is a way to start debugger and then run creator,
this should give results on creator crash. At least i think so.
I do not know how to do it, so i need some time to read, read ....

clochydd

Starting the debugger from the command line:
/.../qtcreator -debug
(/.../qtcreator --help for more options)

deleted28

@> ./qtcreator -debug
The option -debug requires an argument.
... usage etc.
@

Is the necessary argument one of my projects ?

Creator crashes "randomly", i can not reproduce the crash.

Can i use gdb to get any output messages from creator crash ?
If so, how to ?

deleted28

i did
@gdb /opt/Qt5v3/Tools/QtCreator/bin/qtcreator
(gdb) run
@

gdb output (last 10 lines):

@[Thread 0xa1cf8b40 (LWP 5676) exited]
[Thread 0xa3bffb40 (LWP 5675) exited]
[New Thread 0xa3bffb40 (LWP 5677)]
[New Thread 0xa1cf8b40 (LWP 5678)]
Detaching after fork from child process 5679.
[Thread 0xa3bffb40 (LWP 5677) exited]
[Thread 0xa1cf8b40 (LWP 5678) exited]

Program received signal SIGSEGV, Segmentation fault.
0xb710fc17 in QCoreApplication::notifyInternal(QObject*, QEvent*) ()
from /opt/Qt5v3/Tools/QtCreator/bin/../lib/qtcreator/libQt5Core.so.5
(gdb)
@

might this info help ?