[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gdb
Subject:    Re: GDB doesn't interrupt target
From:       Jonah Graham <jonah () kichwacoders ! com>
Date:       2019-12-23 16:31:47
Message-ID: CAPmGMvhHNqFY8_80dJMMk4mMmnU1_Vz9AjX3tTtfKZcnGDUGVg () mail ! gmail ! com
[Download RAW message or body]

On Mon, 23 Dec 2019 at 09:37, Tudor Popescu <popescu.m.tudor@gmail.com> wrote:
> 
> Hello,
> 
> I have tracked the problem to a link:
> Wiki.eclipse.org/CDT/FullGDBConsole.
> Junit test failures #2 and things to work on #1 are the exact descriptions of my \
> problem. The page hasn't been updated since 2016.

Thanks Tudor for pointing out this document on the Wiki - it was a
status report on the development of the new feature and does not
represent the released state of CDT.  I have marked the page as
obsolete.

> Can you tell me how were these issues addressed?

The key part - async comms - cam as part of CDT 9.2 when the new-ui
was rolled out. See the New and Noteworthy:
https://wiki.eclipse.org/CDT/User/NewIn92#Running_All-stop_mode_Asynchronously

Please raise a bug
(https://bugs.eclipse.org/bugs/enter_bug.cgi?product=CDT) in CDT with
the details and I can look at it further. In addition to the version
of those bundles, I need what launch configuration you are using. You
can either share your .launch file, or if that is not possible tell me
what is selected in Debug Configurations dialog on the left (launch
config type) and if present which launcher (this area, next to
revert/apply buttons may be blank). See
https://i.imgur.com/wIkAb0U.png

And it would be most useful to include the MI trace to see what is
going wrong. If it off by default, but you can turn it on in
Preferences -> C/C++ -> Debug -> GDB and check "Show the GDB traces
[...]". Once enabled the Console view will display the MI trace.

I hope we can get to the bottom of this.

Jonah


[prev in list] [next in list] [prev in thread] [next in thread]