Ok, this is what I got: (gdb) run Starting program: /usr/bin/gbx3 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1". [New Thread 0x6eb81460 (LWP 4656)] [New Thread 0x6e176460 (LWP 4657)] [New Thread 0x6d976460 (LWP 4658)]
Program received signal SIGSEGV, Segmentation fault. 0x6ff137ce in ?? () from /usr/lib/arm-linux-gnueabihf/libLLVM-3.5.so.1 (gdb) bt #0 0x6ff137ce in ?? () from /usr/lib/arm-linux-gnueabihf/libLLVM-3.5.so.1 #1 0x6ff13720 in ?? () from /usr/lib/arm-linux-gnueabihf/libLLVM-3.5.so.1 Backtrace stopped: previous frame identical to this frame (corrupt stack?) (gdb) 2015-10-31 0:45 GMT+01:00 Benoît Minisini <gam...@users.sourceforge.net>: > Le 30/10/2015 19:54, Patrik Karlsson a écrit : > > Hi, > > I added the ppa and installed gambas as usual (apt-get install gambas3). > > When I try to start gambas it segfaults. > > > > Is it because of me, the ppa or gambas? :) > > > > pata@rpi2:~$ gambas3 > > > > Segmentation fault (core dumped) > > > > pata@rpi2:~$ gambas3 -V > > > > 3.8.2 > > > > pata@rpi2:~$ uname -a > > Linux rpi2 4.1.10-v7+ #821 SMP PREEMPT Sat Oct 10 00:16:28 BST 2015 > armv7l > > armv7l armv7l GNU/Linux > > If it segfaults, it's not your fault. It may be the ppa, but it is > usually the interpreter. > > Can you provide a stack backtrace of the crash as explained in the §5 of > the "reporting a problem" website page? > > Thanks. > > -- > Benoît Minisini > > > ------------------------------------------------------------------------------ > _______________________________________________ > Gambas-user mailing list > Gambas-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/gambas-user > ------------------------------------------------------------------------------ _______________________________________________ Gambas-user mailing list Gambas-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gambas-user
