[Top][All Lists]

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

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

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #53101] Ctrl+C no longer breaks to gdb prompt
Date: Thu, 8 Feb 2018 20:07:46 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:58.0) Gecko/20100101 Firefox/58.0


                 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



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.

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:


  Message sent via/by Savannah

reply via email to

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