GDB doesn't interrupt target

Tudor Popescu
Mon Dec 23 14:37:00 GMT 2019


I have tracked the problem to a link:
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.
Can you tell me how were these issues addressed?
Maybe it involves just replacing a jar? plugin.

On Friday, December 20, 2019, Jonah Graham <> wrote:
> (resending because last email with embedded picture bounced)
> On Fri, 20 Dec 2019 at 10:37, Tudor Popescu <>
>> Hello,
>> Well we have the following versions:
>> org.eclipse.cdt
>> org.eclipse.cdt.dsf.gdb
>> org.eclipse.cdt.dsf.gdb.ui
> I can't immediately see any significant changes since this version was
> released. However, there are a few patch releases for CDT 9.3, current
> one is 9.3.3 ( (p2
> Have you tried
> with something more recent. The new-ui support was very new when 9.3
> was released, so there may be some bug fixes. In fact, CDT 9.3 was
> released more than a year before the version of GDB you are using.
> While I always hope that we release CDT that will work with future and
> unreleased GDBs, it is hard to be certain of that. Can you please
> report back if this is failing in most recent CDT releases (CDT 9.10
> part of Eclipse 2019-12
> release
>> On Windows, the suspend works. Should it work on Linux as well?
> On Windows there is no new-ui (yet!), so the code paths in Eclipse are
> very different for this. Of course suspend *should* work on both.
> Please raise a bug
> ( 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
> 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.
>> All the best,
>> Tudor
> ~~~
> Jonah Graham
> Kichwa Coders

More information about the Gdb mailing list