Program crashes (SIGSEGV)

[wysota]

@marcel: He doesn't use qmake.

It's enough if you add the -ggdb flag.

[Voldemort]

There changes nothing:

# gdb ./QQMsn 2> ../QQMsn_debug.txt
GNU gdb 6.5
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i586-suse-linux"...Using host libthread_db library "/lib/libthread_db.so.1".

(gdb) run
Starting program: /home/quinten/QQMsn_build/QQMsn
[Thread debugging using libthread_db enabled]
[New Thread -1222338864 (LWP 4290)]
[New Thread -1224852592 (LWP 4297)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1222338864 (LWP 4290)]
0xb66f7d83 in SSL_read () from /usr/lib/libssl.so
(gdb) bt
#0 0xb66f7d83 in SSL_read () from /usr/lib/libssl.so
#1 0x00000004 in ?? ()
#2 0x00000004 in ?? ()
#3 0x00000000 in ?? ()
(gdb) kill
Kill the program being debugged? (y or n) y

But I don't understand a backtrace, how do you have to read it? Where can you find the crucial information in the backtrace?

[marcel]

From what I see in the call stack, it crashes in libssl.
Qt supports SSL from 4.3. Did you link with the correct( required ) ssl library ?
Maybe you didn't have the correct version when you compiled Qt. Anyway, It does not make a lot of sense crashing at that point ( perhaps a bug in Qt related to SSL ? ).

Try disabling SSL from QHttp, if you can...

To Wysota: It doesn't matter if he enables debugging information in his app, because it crashes in another lib.

Regards

[wysota]

To Wysota: It doesn't matter if he enables debugging information in his app, because it crashes in another lib.

Of course it matters - something calls this "another lib", right?. As you can see three symbols are not identified correctly. And it looks like a corrupted stack (look at symbol addresses, it looks like the frame stack is incorrect), by the way, so I suggest doing "make distclean && qmake && make" first to make sure the app is compiled properly. Blaiming OpenSSL is certainly not the way to go.