GithubHelp home page GithubHelp logo

target-async is deprecated about cdt HOT 7 CLOSED

eclipse-cdt avatar eclipse-cdt commented on July 24, 2024
target-async is deprecated

from cdt.

Comments (7)

jonahgraham avatar jonahgraham commented on July 24, 2024 1

Its all handled with my patch. stepSetNonStop is already overridden in FinalLaunchSequence_7_12

from cdt.

jld01 avatar jld01 commented on July 24, 2024

@Torbjorn-Svensson we don't use -gdb-set target-async on for GDB versions prior to org.eclipse.cdt.dsf.gdb.launching.FinalLaunchSequence_7_12 so it seems safe to modify stepSetTargetAsync to call a new stepSetMIAsync method within that class. If we modify org.eclipse.cdt.dsf.gdb.launching.FinalLaunchSequence_7_12.getExecutionOrder(String) to use the new step there is a possibility that we will break run-time behaviour of extenders that are modifying the execution order based on the position of stepSetTargetAsync, but CDT 11.0.0 seems a good time to make such a change.

from cdt.

Torbjorn-Svensson avatar Torbjorn-Svensson commented on July 24, 2024

Do you think we can keep the stepSetTargetAsync but leave the implementation empty and then add a new stepSetTargetAsync or would that still break run-time behavior for extenders?

I agree that CDT11 is a good time this type of change, but I don't know if the time has run out for doing it...

@jonahgraham WDYT? Is this something that we should do?

I'm slammed with work for the rest of the week, so if one of you could look at this (if it's something we want to do for CDT11), I'd appreciate it.

from cdt.

jonahgraham avatar jonahgraham commented on July 24, 2024

Please have a look at #177 that fixes this.

from cdt.

jonahgraham avatar jonahgraham commented on July 24, 2024

we don't use -gdb-set target-async on for GDB versions prior to

Actually we do, in non-stop mode in all versions of GDB:

fCommandControl.queueCommand(fCommandFactory.createMIGDBSetTargetAsync(fCommandControl.getContext(), true),

from cdt.

jld01 avatar jld01 commented on July 24, 2024

we don't use -gdb-set target-async on for GDB versions prior to

Actually we do, in non-stop mode in all versions of GDB:

I missed that one. Could we override stepSetNonStop in FinalLaunchSequence_7_12? Or perhaps introduce a protected boolean hasGDBSetMIAsync() method in FinalLaunchSequence and override that in FinalLaunchSequence_7_12 ?

from cdt.

jonahgraham avatar jonahgraham commented on July 24, 2024

public void stepSetNonStop(final RequestMonitor requestMonitor) {

from cdt.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.