From: Jonah Graham <jonah@kichwacoders.com>
To: Tudor Popescu <popescu.m.tudor@gmail.com>
Cc: Pedro Alves <palves@redhat.com>, GDB Development <gdb@sourceware.org>
Subject: Re: GDB doesn't interrupt target
Date: Mon, 23 Dec 2019 16:32:00 -0000 [thread overview]
Message-ID: <CAPmGMvhHNqFY8_80dJMMk4mMmnU1_Vz9AjX3tTtfKZcnGDUGVg@mail.gmail.com> (raw)
In-Reply-To: <CAHrp7QDosAYw2k+i2L-gcY-ZLaH9Anaq2HonAZphOcps8SLoMg@mail.gmail.com>
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 parent reply other threads:[~2019-12-23 16:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 14:20 Tudor Popescu
2019-12-18 14:59 ` Pedro Alves
2019-12-18 15:49 ` Jonah Graham
[not found] ` <CAHrp7QDmyiyyXtpcA_XSN41=eZM3eT3vwhuY5e9WTCqHGD_k1g@mail.gmail.com>
2019-12-19 14:22 ` Pedro Alves
2019-12-19 14:47 ` Jonah Graham
2019-12-20 15:37 ` Tudor Popescu
2019-12-20 16:23 ` Jonah Graham
2019-12-23 14:37 ` Tudor Popescu
2019-12-23 16:32 ` Jonah Graham [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPmGMvhHNqFY8_80dJMMk4mMmnU1_Vz9AjX3tTtfKZcnGDUGVg@mail.gmail.com \
--to=jonah@kichwacoders.com \
--cc=gdb@sourceware.org \
--cc=palves@redhat.com \
--cc=popescu.m.tudor@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox