octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug #44478


From: Juan Pablo Carbajal
Subject: bug #44478
Date: Mon, 16 Mar 2015 18:45:11 +0100

Hello Rik and list,

I am trying to follow the instructions you gave in comment #37
https://savannah.gnu.org/bugs/?44478

Everything goers ok until I run octave with the -g argument.

GDB starts with a complaint about file format and suggests to add some
safe-path to .gdbinit...aynways the gdb prompt appears.

when I execute the run command I get a lots of print for the paths and suddenly

[1]+  Stopped                 ./run-octave -g -f --no-gui

Is this normal?

Since this brings me back to the system prompt I run "fg" to continue
with the execution. At this point I get

./run-octave -g -f --no-gui
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
process 24213 is executing new program: /bin/bash
process 24213 is executing new program:
/home/juanpi/Downloads/octave-4.0.0-rc1/src/.libs/lt-octave-gui
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffd8962700 (LWP 24238)]
[New Thread 0x7fffd3fff700 (LWP 24239)]
[New Thread 0x7fffcbded700 (LWP 24240)]
[New Thread 0x7fffcb5ec700 (LWP 24241)]
[New Thread 0x7fffcadeb700 (LWP 24242)]
[New Thread 0x7fffca5ea700 (LWP 24244)]
GNU Octave, version 4.0.0-rc1
Copyright (C) 2015 John W. Eaton and others.
This is free software; see the source code for copying conditions.
There is ABSOLUTELY NO WARRANTY; not even for MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE.  For details, type 'warranty'.

Octave was configured for "x86_64-unknown-linux-gnu".

Additional information about Octave is available at http://www.octave.org.

Please contribute if you find this software useful.
For more information, visit http://www.octave.org/get-involved.html

Read http://www.octave.org/bugs.html to learn how to submit bug reports.
For information about changes from previous versions, type 'news'.


Program received signal SIGTTOU, Stopped (tty output).
[Switching to Thread 0x7fffca5ea700 (LWP 24244)]
0x00007ffff45055ca in __GI_tcsetattr (fd=0, optional_actions=<optimized out>,
    termios_p=0x7fffca5e9460) at ../sysdeps/unix/sysv/linux/tcsetattr.c:87
87 ../sysdeps/unix/sysv/linux/tcsetattr.c: No such file or directory.


At this point I am back into the gdb prompt and if I run "continue" I
keep getting this errors with other files.

Any idea what's happening?



reply via email to

[Prev in Thread] Current Thread [Next in Thread]