Dear maintainer,
I tried to start scilab with debugging mode. I look at schlub web site
:"https://wiki.scilab.org/Debugging%20and%20Profiling%20Scilab%205";
I used the procedure with gdb. I put the shell return.

dagmat@mc-queen:/usr/bin$ scilab -debug
Running debug of Scilab [gdb]  :  gdb --args /usr/bin/scilab-bin -debug
GNU gdb (Debian 7.10-1+b1) 7.10
Copyright (C) 2015 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-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/scilab-bin...Reading symbols from
/usr/lib/debug//usr/bin/scilab-bin...done.
done.
(gdb) run  -ns  -nwni -f
modules/functions/scripts/buildmacros/buildmacros.sce
Starting program: /usr/bin/scilab-bin -ns  -nwni -f
modules/functions/scripts/buildmacros/buildmacros.sce
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe2d57700 (LWP 5653)]
[New Thread 0x7fffe2556700 (LWP 5654)]
[New Thread 0x7fffddd55700 (LWP 5655)]
[New Thread 0x7fffdb554700 (LWP 5656)]
[New Thread 0x7fffd8d53700 (LWP 5657)]
[New Thread 0x7fffd8552700 (LWP 5658)]
[New Thread 0x7fffd3d51700 (LWP 5659)]
Scilab startup function detected that the function proposed to the
engine is the wrong one. Usually, it comes from a linker problem in your
distribution/OS.
Here, Scilab should have 'libscijvm-disable' defined but gets
'libscijvm' instead.
If you do not know what it means, please report a bug on
http://bugzilla.scilab.org/. If you do, you probably know that you
should change the link order in SCI/modules/Makefile.am
[Thread 0x7fffd3d51700 (LWP 5659) exited]
[Thread 0x7fffd8552700 (LWP 5658) exited]
[Thread 0x7fffd8d53700 (LWP 5657) exited]
[Thread 0x7fffdb554700 (LWP 5656) exited]
[Thread 0x7fffddd55700 (LWP 5655) exited]
[Thread 0x7fffe2556700 (LWP 5654) exited]
[Thread 0x7fffe2d57700 (LWP 5653) exited]
[Inferior 1 (process 5649) exited with code 01]
(gdb)

With my script
(gdb) run  -ns  -nwni -f
/home/dagmat/THESE/2015/prog_similitude/test1/essai_2_elem_v2.sce
Starting program: /usr/bin/scilab-bin -ns  -nwni -f
/home/dagmat/THESE/2015/prog_similitude/test1/essai_2_elem_v2.sce
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe2d57700 (LWP 5686)]
[New Thread 0x7fffe2556700 (LWP 5687)]
[New Thread 0x7fffddd55700 (LWP 5688)]
[New Thread 0x7fffdb554700 (LWP 5689)]
[New Thread 0x7fffd8d53700 (LWP 5690)]
[New Thread 0x7fffd8552700 (LWP 5691)]
[New Thread 0x7fffd3d51700 (LWP 5692)]
Scilab startup function detected that the function proposed to the
engine is the wrong one. Usually, it comes from a linker problem in your
distribution/OS.
Here, Scilab should have 'libscijvm-disable' defined but gets
'libscijvm' instead.
If you do not know what it means, please report a bug on
http://bugzilla.scilab.org/. If you do, you probably know that you
should change the link order in SCI/modules/Makefile.am
[Thread 0x7fffd3d51700 (LWP 5692) exited]
[Thread 0x7fffd8552700 (LWP 5691) exited]
[Thread 0x7fffd8d53700 (LWP 5690) exited]
[Thread 0x7fffdb554700 (LWP 5689) exited]
[Thread 0x7fffddd55700 (LWP 5688) exited]
[Thread 0x7fffe2556700 (LWP 5687) exited]
[Thread 0x7fffe2d57700 (LWP 5686) exited]
[Inferior 1 (process 5685) exited with code 01]
(gdb)

Nice day, thanks for your help
Mathieu DAGOIS

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Reply via email to