Re: [Gambas-user] Segmentation fault (core dumped)
Brought to you by:
gambas
From: Dr.Diesel <dr....@gm...> - 2010-02-28 03:08:56
|
Don't think so, but i do have one default printer setup, it works fine though? I deleted my default printer and gambas now works fine! This is very weird? I am guessing I need to report this to my distro, what do you think? As always, many thanks! Bugzilla from ga...@us... wrote: > >> Bugzilla from ga...@us... wrote: >> >> Fabien Bodard-4 wrote: >> >> > no you are not in the good path ! >> >> > >> >> > >> >> > cd /home/george/trunk/app/src/gambas3 >> >> > gdb gbx3 >> >> > >> >> >>set args -p >> >> >>run >> >> >> >> >> > ..... segfault >> >> > >> >> >>bt >> >> >> >> >> > return the output >> >> >> >> Mmmmmm, that didn't catch the crash? Notice at the bottom I run >> >> gambas3, thanks for the help! >> > >> > You must recompile the project before, because it has been cleaned by >> > "make >> > install". >> > >> > [george@george gambas3]$ gbc3 -agt >> > OK >> > [george@george gambas3]$ gdb gbx3 >> > ... >> > >> > Regards, >> >> Thank you, finally something useful! >> >> [george@george gambas3]$ gdb gbx3 >> GNU gdb (GDB) Fedora (7.0.1-32.fc12) >> Copyright (C) 2009 Free Software Foundation, Inc. >> License GPLv3+: GNU GPL version 3 or later >> <http://gnu.org/licenses/gpl.html> >> This is free software: you are free to change and redistribute it. >> There is NO WARRANTY, to the extent permitted by law. Type "show >> copying" >> and "show warranty" for details. >> This GDB was configured as "x86_64-redhat-linux-gnu". >> For bug reporting instructions, please see: >> <http://www.gnu.org/software/gdb/bugs/>... >> Reading symbols from /usr/local/bin/gbx3...done. >> (gdb) set args -p >> (gdb) run >> Starting program: /usr/local/bin/gbx3 -p >> [Thread debugging using libthread_db enabled] >> warning: "/usr/lib/debug/usr/lib64/libQt3Support.so.4.6.2.debug": >> separate >> debug info file has no debug info >> warning: "/usr/lib/debug/usr/lib64/libQtWebKit.so.4.6.2.debug": separate >> debug info file has no debug info >> Detaching after fork from child process 24914. >> Detaching after fork from child process 24916. >> Detaching after fork from child process 24917. >> [New Thread 0x7fffeb243710 (LWP 24919)] >> >> Program received signal SIGSEGV, Segmentation fault. >> 0x0000003b2c124cd1 in QPrinter::QPrinter (this=<value optimized out>, >> mode=<value optimized out>) >> at painting/qprinter.cpp:658 >> 658 if( cups.currentPPD()->color_device ) >> (gdb) bt >> #0 0x0000003b2c124cd1 in QPrinter::QPrinter (this=<value optimized out>, >> mode=<value optimized out>) >> at painting/qprinter.cpp:658 >> #1 0x00007ffff7978a67 in Printer_new (_object=0xe19e70, _param=<value >> optimized out>) >> at cprinter.cpp:168 >> #2 0x0000000000407519 in EXEC_call_native (exec=0xe4fbb8, >> object=0x7fffffffc420, type=0, >> param=<value optimized out>) at gbx_exec.c:979 >> #3 0x000000000040813f in EXEC_native () at gbx_exec.c:1180 >> #4 0x00000000004091c8 in EXEC_special (special=<value optimized out>, >> class=<value optimized out>, >> object=<value optimized out>, nparam=0, drop=<value optimized out>) >> at >> gbx_exec.c:1485 >> #5 0x00000000004094d4 in EXEC_special_inheritance (special=0, >> class=0x66dc60, object=0xe19e70, nparam= >> 0, drop=1 '\001') at gbx_exec.c:1627 >> #6 0x0000000000409bde in EXEC_new () at gbx_exec.c:1837 >> #7 0x0000000000429215 in EXEC_loop () at gbx_exec_loop.c:820 >> #8 0x0000000000408c96 in EXEC_function_loop () at gbx_exec.c:795 >> #9 0x0000000000409050 in EXEC_function_real () at gbx_exec.c:782 >> #10 0x00000000004095b5 in EXEC_special_inheritance (special=0, >> class=0x93b100, object=0xe098e0, >> nparam=<value optimized out>, drop=<value optimized out>) at >> gbx_exec.c:1673 >> #11 0x000000000041f0c2 in OBJECT_create (object=<value optimized out>, >> class=<value optimized out>, >> name=<value optimized out>, parent=<value optimized out>, >> nparam=<value >> optimized out>) >> at gbx_object.c:369 >> #12 0x000000000040bca3 in CLASS_auto_create (class=0x93b100, nparam=0) at >> gbx_class.c:1077 >> #13 0x00007ffff795151d in CFORM_load (_object=<value optimized out>, >> _param=<value optimized out>) >> at CWindow.cpp:475 >> #14 0x0000000000407519 in EXEC_call_native (exec=0xe4fbb8, >> object=0x7fffffffc420, type=0, >> param=<value optimized out>) at gbx_exec.c:979 >> #15 0x000000000040813f in EXEC_native () at gbx_exec.c:1180 >> #16 0x0000000000429201 in EXEC_loop () at gbx_exec_loop.c:975 >> #17 0x0000000000408c96 in EXEC_function_loop () at gbx_exec.c:795 >> ---Type <return> to continue, or q <return> to quit--- >> #18 0x0000000000409050 in EXEC_function_real () at gbx_exec.c:782 >> #19 0x00000000004091e3 in EXEC_special (special=<value optimized out>, >> class=<value optimized out>, >> object=<value optimized out>, nparam=0, drop=<value optimized out>) >> at >> gbx_exec.c:1493 >> #20 0x00000000004096e2 in EXEC_special_inheritance (special=0, >> class=0x914980, object=0x9a5cc0, >> nparam=<value optimized out>, drop=<value optimized out>) at >> gbx_exec.c:1720 >> #21 0x000000000041f0c2 in OBJECT_create (object=<value optimized out>, >> class=<value optimized out>, >> name=<value optimized out>, parent=<value optimized out>, >> nparam=<value >> optimized out>) >> at gbx_object.c:369 >> #22 0x000000000040bca3 in CLASS_auto_create (class=0x914980, nparam=0) at >> gbx_class.c:1077 >> #23 0x00007ffff795151d in CFORM_load (_object=<value optimized out>, >> _param=<value optimized out>) >> at CWindow.cpp:475 >> #24 0x0000000000407519 in EXEC_call_native (exec=0xe4fbb8, >> object=0x7fffffffc420, type=0, >> param=<value optimized out>) at gbx_exec.c:979 >> #25 0x000000000040813f in EXEC_native () at gbx_exec.c:1180 >> #26 0x0000000000429201 in EXEC_loop () at gbx_exec_loop.c:975 >> #27 0x0000000000408c96 in EXEC_function_loop () at gbx_exec.c:795 >> #28 0x0000000000409050 in EXEC_function_real () at gbx_exec.c:782 >> #29 0x000000000041e218 in main (argc=1, argv=<value optimized out>) at >> gbx.c:356 >> (gdb) > > It seems to be a bug in Qt. Do you have some specific printer > configuration? > > -- > Benoît Minisini > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Gambas-user mailing list > Gam...@li... > https://lists.sourceforge.net/lists/listinfo/gambas-user > > -- View this message in context: http://old.nabble.com/Segmentation-fault-%28core-dumped%29-tp27728610p27732762.html Sent from the gambas-user mailing list archive at Nabble.com. |