[Octave-bug-tracker] [bug #53101] Ctrl+C no longer breaks to gdb prompt

[Mike Miller]

URL:
  <http://savannah.gnu.org/bugs/?53101>

                 Summary: Ctrl+C no longer breaks to gdb prompt
                 Project: GNU Octave
            Submitted by: mtmiller
            Submitted on: Thu 08 Feb 2018 05:07:45 PM PST
                Category: Interpreter
                Severity: 4 - Important
                Priority: 5 - Normal
              Item Group: Regression
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: GNU/Linux

    _______________________________________________________

Details:

When running octave-cli under gdb, it used to be possible to


$ gdb --args octave-cli
...
(gdb) run
...
>> ^C
Thread 1 "octave-cli" received signal SIGINT, Interrupt.
...
(gdb) 


Now octave seems to catch the Ctrl+C itself and not allow control to be
returned to the debugger.

If this is an improvement to make Ctrl+C more robust in octave, that's ok, but
is there any way to work interactively with a debugger now?




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?53101>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/