crash on new machine: terminate called after throwing an ins

Typically: "How do I... ", "How can I... " questions
Post Reply
fferri
Posts: 173
Joined: 09 Sep 2013, 19:28

crash on new machine: terminate called after throwing an ins

Post by fferri » 14 Apr 2015, 16:32

I got a new machine, installed Ubuntu 14.04.2, and V-REP 3.2.0rev6.

When launching V-REP, it crashes with this error:

Code: Select all

$ ./vrep.sh
Add-on script 'vrepAddOnScript-addOnScriptDemo.lua' was loaded.
terminate called after throwing an instance of 'std::exception'
  what():  std::exception
Aborted (core dumped)
Running in the debugger to get a stacktrace:

Code: Select all

$ export LD_LIBRARY_PATH=$PWD
$ gdb vrep
GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.2) 7.7.1
Reading symbols from vrep...(no debugging symbols found)...done.
(gdb) r
Starting program: /opt/V-REP_PRO_EDU_V3_2_0_rev6_64_Linux/vrep 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffea9ed700 (LWP 8876)]
[New Thread 0x7fffe0787700 (LWP 8877)]
[New Thread 0x7fffdff86700 (LWP 8878)]
[New Thread 0x7fffde421700 (LWP 8879)]
[New Thread 0x7fffddc20700 (LWP 8880)]
[New Thread 0x7fffdd41f700 (LWP 8881)]
[Thread 0x7fffddc20700 (LWP 8880) exited]
Add-on script 'vrepAddOnScript-addOnScriptDemo.lua' was loaded.
terminate called after throwing an instance of 'std::exception'
  what():  std::exception

Program received signal SIGABRT, Aborted.
0x00007ffff6bd7cc9 in __GI_raise (sig=sig@entry=6)
    at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
56	../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  0x00007ffff6bd7cc9 in __GI_raise (sig=sig@entry=6)
    at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1  0x00007ffff6bdb0d8 in __GI_abort () at abort.c:89
#2  0x00007ffff71dc6b5 in __gnu_cxx::__verbose_terminate_handler() ()
   from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#3  0x00007ffff71da836 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#4  0x00007ffff71da863 in std::terminate() ()
   from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#5  0x00007ffff71daaa2 in __cxa_throw ()
   from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#6  0x00007ffff3376369 in VFile::VFile(std::string const&, unsigned short, bool) () from /opt/V-REP_PRO_EDU_V3_2_0_rev6_64_Linux/libv_rep.so
#7  0x00007ffff34e13d0 in CFolderThumbnails::prepareFolderThumbnails(char const*) () from /opt/V-REP_PRO_EDU_V3_2_0_rev6_64_Linux/libv_rep.so
#8  0x00007ffff343dab6 in CMainContainer::initialize(bool) ()
   from /opt/V-REP_PRO_EDU_V3_2_0_rev6_64_Linux/libv_rep.so
#9  0x00007ffff36b6f9b in App::createMainContainer() ()
   from /opt/V-REP_PRO_EDU_V3_2_0_rev6_64_Linux/libv_rep.so
#10 0x00007ffff353c210 in simRunSimulator_internal(char const*, int, void (*)(), void (*)(), void (*)()) ()
   from /opt/V-REP_PRO_EDU_V3_2_0_rev6_64_Linux/libv_rep.so
#11 0x00000000004028cb in main ()
(gdb) 
This is very strange, I got the same version of V-REP on the same version of Ubuntu on another machine, and works fine.

Any ideas?

coppelia
Site Admin
Posts: 6625
Joined: 14 Dec 2012, 00:25

Re: crash on new machine: terminate called after throwing an

Post by coppelia » 15 Apr 2015, 08:42

Hello,

can you try to turn on all debugging info? You can do this in file system/usrset.txt. Beware that when outputting debug info, V-REP will become very slow, so do not forget to turn it off later on again.

Cheers

fferri
Posts: 173
Joined: 09 Sep 2013, 19:28

Re: crash on new machine: terminate called after throwing an

Post by fferri » 15 Apr 2015, 09:31

I don't have such file

coppelia
Site Admin
Posts: 6625
Joined: 14 Dec 2012, 00:25

Re: crash on new machine: terminate called after throwing an

Post by coppelia » 15 Apr 2015, 10:13

do you have the folder system? How did you install V-REP?

Cheers

fferri
Posts: 173
Joined: 09 Sep 2013, 19:28

Re: crash on new machine: terminate called after throwing an

Post by fferri » 15 Apr 2015, 10:19

yes, I have the system folder, but there is no such file:

Code: Select all

$ ls -1 /opt/V-REP_PRO_EDU_V3_2_0_rev6_64_Linux/system/
defaultContactCallbackScript.txt
defaultCustomizationScript.txt
defaultGeneralCallbackScript.txt
defaultJointCtrlCallbackScript.txt
dfltscn.ttt
dltcscpt.txt
dltmscpt.txt
dlttscpt.txt
sysnfo.ttb

coppelia
Site Admin
Posts: 6625
Joined: 14 Dec 2012, 00:25

Re: crash on new machine: terminate called after throwing an

Post by coppelia » 15 Apr 2015, 11:08

Ok, if you modify a user setting, the file will be generated. Check for instance [Menu bar --> Help --> Debug --> Debug internal...], which will generate the file.

Cheers

oKermorgant
Posts: 2
Joined: 06 Dec 2016, 13:10

Re: crash on new machine: terminate called after throwing an ins

Post by oKermorgant » 16 May 2018, 12:20

I got to this page after encountering the same error message (vrep std exception).

My installation is the same as the OP, with V-REP in /opt.

It happens that the V-REP folder should be writable by the current user.
The installation in /opt is usually done so that all user can run V-REP, in this case the folder should have lighter permissions :

Code: Select all

sudo chmod -R a+rwX /opt/vrep

Post Reply