[Top][All Lists]

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

[Octave-bug-tracker] [bug #59100] "__debug_octave__" doesn't work on Win

From: Rik
Subject: [Octave-bug-tracker] [bug #59100] "__debug_octave__" doesn't work on Windows
Date: Sat, 12 Sep 2020 16:33:11 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.83 Safari/537.36

Update of bug #59100 (project octave):

                Priority:              5 - Normal => 3 - Low                
                  Status:                    None => Need Info              


Follow-up Comment #1:

The second output being undefined is a different issue.  You could open a new
bug report for that.

As for the first part of this report, the "start" program should launch a new
Command Window and shell and then run the specified command.  If it is somehow
re-using the existing Command Window where Octave is running then there is
probably a problem with how we are using "start".

The documentation for the command is at

Can you experiment with some of the options?  Perhaps "/wait" or "/elevate"
need to be thrown?  Also in testing, use the command which includes "gdb -p
%d" where %d is replaced by the results of getpid().


Reply to this item at:


  Message sent via Savannah

reply via email to

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