Benoît Minisini schreef: >> Benoit, >> Here is the output of valgrind as requested. I hope it helps. >> Regards, >> Tony.. >> $ valgrind --tool=memcheck --num-callers=50 gbx2 >> ==2404== Memcheck, a memory error detector >> ==2404== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al. >> ==2404== Using Valgrind-3.5.0-Debian and LibVEX; rerun with -h for >> copyright info >> ==2404== Command: gbx2 >> ==2404== >> /dev/ttyUSB0 >> 19200 >> 0 >> 8 >> 1 >> 1 >> 1 >> ==2404== Invalid read of size 4 >> ==2404== at 0x535C586: CSerialPort_CallBack (CSerialPort.c:120) >> ==2404== by 0x4663A21: CWatch::write(int) (CWatch.cpp:143) >> ==2404== by 0x4663885: CWatch::qt_invoke(int, QUObject*) >> (CWatch_moc.cpp:91) >> ... >> > > Is it better with revision #2455? (Ron, you can try too!) > > I guess not...
Program received signal SIGSEGV, Segmentation fault. GB_Raise (object=0xd, event_id=0, nparam=0) at gbx_api.c:528 528 OBJECT_REF(object, "GB_Raise"); (gdb) bt #0 GB_Raise (object=0xd, event_id=0, nparam=0) at gbx_api.c:528 #1 0x00334cd5 in CSerialPort_ReadCallBack (_object=0xd) at CSerialPort.c:175 #2 0x08060997 in raise_callback (wait=<value optimized out>) at gbx_watch.c:425 #3 do_loop (wait=<value optimized out>) at gbx_watch.c:498 #4 0x08060b04 in WATCH_loop () at gbx_watch.c:530 #5 0x08061b72 in main (argc=134739040, argv=0xbffff4f4) at gbx.c:358 (gdb) ==5235== Memcheck, a memory error detector ==5235== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al. ==5235== Using Valgrind-3.5.0-Debian and LibVEX; rerun with -h for copyright info ==5235== Command: gbx2 -p ==5235== Parent PID: 16998 ==5235== ==5235== Invalid read of size 4 ==5235== at 0x805D8DA: GB_Raise (gbx_api.c:528) ==5235== by 0x460CCD4: CSerialPort_ReadCallBack (CSerialPort.c:175) ==5235== by 0x8060996: do_loop (gbx_watch.c:425) ==5235== by 0x8060B03: WATCH_loop (gbx_watch.c:530) ==5235== by 0x8061B71: main (gbx.c:358) ==5235== Address 0x10 is not stack'd, malloc'd or (recently) free'd ==5235== ==5235== ==5235== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==5235== Access not within mapped region at address 0x10 ==5235== at 0x805D8DA: GB_Raise (gbx_api.c:528) ==5235== by 0x460CCD4: CSerialPort_ReadCallBack (CSerialPort.c:175) ==5235== by 0x8060996: do_loop (gbx_watch.c:425) ==5235== by 0x8060B03: WATCH_loop (gbx_watch.c:530) ==5235== by 0x8061B71: main (gbx.c:358) ==5235== If you believe this happened as a result of a stack ==5235== overflow in your program's main thread (unlikely but ==5235== possible), you can try to increase the size of the ==5235== main thread stack using the --main-stacksize= flag. ==5235== The main thread stack size used in this run was 8388608. Regards, Ron_2nd. ------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________ Gambas-user mailing list Gambas-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gambas-user