Re: [Lazarus] [Qt] Random issues at startup
On 2015-02-23 16:42, Vojtěch Čihák wrote: And I observed (with breakpoints in *.lpr) that the malloc ... message comes from Application.Initialize; fpc 2.6.4 or 3.XX ? -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] [Qt] Random issues at startup
It is Lazarus 1.5 r47939M FPC 3.1.1 x86_64-linux-qt __ Od: zel...@holobit.net Komu: Lazarus mailing list lazarus@lists.lazarus.freepascal.org Datum: 24.02.2015 18:00 Předmět: Re: [Lazarus] [Qt] Random issues at startup On 2015-02-23 16:42, Vojtěch Čihák wrote: And I observed (with breakpoints in *.lpr) that the malloc ... message comes from Application.Initialize; fpc 2.6.4 or 3.XX ? -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
[Lazarus] [Qt] Random issues at startup
Hi, I work on app. (~2 lines) and sometimes at startup (10 - 15% cases of hiting F9) I got this message in console: malloc(): smallbin double linked list corrupted: 0x010ee860 *** and it crashes. (Note that it is only in Qt, the same app. in GTK2 is OK.) CallStack window doesn't show me anything.Google doesn't help much, I didn't find anything Lazarus-related but I found a few Qt related topics - one of them recommende valgrind.So I tried valgrind and KCacheGrind$ valgrind --tool=callgrind ./myprogrambut it also didn't help me much (maybe I do it wrong ?). The last line of output is pointing to libQtCore.so.4.8.6I don't want to publish code yet and I cannot reproduce with a small demo.Thanks for help,Vojtěch -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] [Qt] Random issues at startup
On 2015-02-23 09:10, Vojtěch Čihák wrote: Hi, I work on app. (~2 lines) and sometimes at startup (10 - 15% cases of hiting F9) I got this message in console: malloc(): smallbin double linked list corrupted: 0x010ee860 *** and it crashes. (Note that it is only in Qt, the same app. in GTK2 is OK.) CallStack window doesn't show me anything. Google doesn't help much, I didn't find anything Lazarus-related but I found a few Qt related topics - one of them recommende valgrind. So I tried valgrind and KCacheGrind $ valgrind --tool=callgrind ./myprogram but it also didn't help me much (maybe I do it wrong ?). The last line of output is pointing to libQtCore.so.4.8.6 I don't want to publish code yet and I cannot reproduce with a small demo. Without code I can do exactly nothing. Are U using LCL code only or you include qt4 somewhere and use pure qt api. If it's something up to qtlcl then gdb should show it. 32 or 64 bit ? What distro (Qt packager) ? z. -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] [Qt] Random issues at startup
The code is LCL only. I do not use Qt directly.
It is Chakra linux, 64-bit. Qt 4.8.6. I tried FpDebug and gdb again.
When it crashes (after ~ 5 attempts) and I press Pause, CallStack gives this:
#0 __lll_lock_wait_private at :0
#1 malloc at :0
#2 _dl_map_object_deps at :0
#3 dl_open_worker at :0
#4 _dl_catch_error at :0
#5 _dl_open at :0
#6 do_dlopen at :0
#7 _dl_catch_error at :0
#8 dlerror_run at :0
#9 __libc_dlopen_mode at :0
#10 init at :0
#11 pthread_once at :0
#12 backtrace at :0
#13 backtrace_and_maps at :0
#14 __libc_message at :0
#15 malloc_printerr at :0
#16 _int_malloc at :0
#17 malloc at :0
#18 operator new(unsigned long) at :0
#19 QMutexPool::createMutex(int) at :0
#20 ?? at :0
#21 QObject::connect(QObject const*, char const*, QObject const*, char const*,
Qt::ConnectionType) at :0
#22 QObject_hook_create at :0
#23 APPINIT(0xfedc88, {PIXELSPERINCHX = 72, PIXELSPERINCHY = 72, COLORDEPTH =
24, INITIALIZED = false}) at qt/qtobject.inc:228
#24 INITIALIZE(0xfed2b8) at include/application.inc:445
#25 main at ecsas.lpr:23
__
Od: zel...@holobit.net
Komu: Lazarus mailing list lazarus@lists.lazarus.freepascal.org
Datum: 23.02.2015 21:03
Předmět: Re: [Lazarus] [Qt] Random issues at startup
On 2015-02-23 09:10, Vojtěch Čihák wrote:
Hi,
I work on app. (~2 lines) and sometimes at startup (10 - 15% cases
of hiting F9) I got this message in console:
malloc(): smallbin double linked list corrupted: 0x010ee860
***
and it crashes.
(Note that it is only in Qt, the same app. in GTK2 is OK.)
CallStack window doesn't show me anything.
Google doesn't help much, I didn't find anything Lazarus-related but I
found a few Qt related topics - one of them recommende valgrind.
So I tried valgrind and KCacheGrind
$ valgrind --tool=callgrind ./myprogram
but it also didn't help me much (maybe I do it wrong ?). The last line
of output is pointing to libQtCore.so.4.8.6
I don't want to publish code yet and I cannot reproduce with a small
demo.
Without code I can do exactly nothing. Are U using LCL code only or you
include qt4 somewhere and use pure qt api. If it's something up to qtlcl
then gdb should show it. 32 or 64 bit ? What distro (Qt packager) ?
z.
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] [Qt] Random issues at startup
And I observed (with breakpoints in *.lpr) that the malloc ... message comes from Application.Initialize; V. __ -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
