Hi, I did as you told me. Now, the strangest thing happened : The error vanished !
Valgrind gives me just a few lines. Saying that, apart from some memory lost, nothing is wrong. I tried to run the program as normally is done, no problem. All is fine. Only, I have the impression it's a bit slower .. possible ? So, is it ok now, or do you want me to do other test ? Thanks, and regards, Steven Le mardi 08 février 2011 à 18:25 +0100, Benoît Minisini a écrit : > > After some testing, i found out I had to set the scaled parm to false > > for all the windows. > > So, now I succeeded the first part. The output is : > > > > steven@localhost:~/request_dev> gbx2 -p > > kbuildsycoca running... > > QObject::disconnect: Unexpected null parameter > > steven@localhost:~/request_dev> gbx2 -p > > kbuildsycoca running... > > Erreur de segmentation (core dumped) > > steven@localhost:~/request_dev> DCOP Cleaning up dead connections. > > > > steven@localhost:~/request_dev> gdb /usr/bin/gbx2 core > > GNU gdb (GDB) SUSE (6.8.91.20090930-2.4) > > 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 > > "i586-suse-linux". > > For bug reporting instructions, please see: > > <http://www.gnu.org/software/gdb/bugs/>... > > Reading symbols from /usr/bin/gbx2...(no debugging symbols > > found)...done. > > Missing separate debuginfo for /lib/ld-linux.so.2 > > Try: zypper install -C > > "debuginfo(build-id)=43b505ea5e193fa5d7c742793989c5aaa0874e0c" > > Core was generated by `gbx2 -p'. > > Program terminated with signal 11, Segmentation fault. > > #0 0xb48f12d7 in ?? () > > (gdb) bt > > #0 0xb48f12d7 in ?? () > > #1 0xb48f13fb in ?? () > > #2 0xb78a9a6f in ?? () > > #3 0xb78a6f8f in ?? () > > #4 0x0804e4e0 in getgid () > > #5 0x081b0250 in ?? () > > #6 0x0804ede4 in getgid () > > #7 0xb78a6f01 in ?? () > > #8 0x0806aeb0 in getgid () > > #9 0x08088d08 in ?? () > > #10 0x0804f0e5 in getgid () > > #11 0xffffffff in ?? () > > #12 0x0804f3bb in getgid () > > #13 0xbff34afc in ?? () > > #14 0x0805cf10 in getgid () > > #15 0x08610f58 in ?? () > > #16 0x0805d40e in getgid () > > #17 0x00000000 in ?? () > > (gdb) quit > > steven@localhost:~/request_dev> > > > > I dont know if this helps, do i do that (installing debug info) ? > > > > Steven > > > > I should have been more precise: > > - You must first uninstall the old gambas2 binary packages. > - Then you can compile and install gambas2 from the trunk. > - When you compile gambas2, dont' do just "make", but the following: > > $ make "CFLAGS=-O0 -g" "CXXFLAGS=-O0 -g" > > - Once everything is correctly installed, you can start valgrind again and > get > more useful details for me. > > P.S. I got your valgrind output post, but it was too big to be sent to the > entire mailing-list (a post cannot be heavier than 256 Kb). > > Regards, > ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Gambas-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gambas-user
