User forums > Using Code::Blocks
Is it possible to debugging executables not compiled with code::blocks ?
advance-software:
> setup you executable paths and then disable the option "Settings -> Debugger -> auto build project if it is not up to data"
"Settings -> Debugger -> auto build project is a global setting so I'd have to remember to switch this on/off as I switch projects. That might work but it's not a good solution.
So it's time to enter makefile hell ... yay.
The point is rather than everyone figuring their way around a quirky system, a more intuitive interface will make support easier and the product better. If your motivation is just to add the stuff you need/use, that's fair enough I suppose. Such is free software ...
update :
> setup you executable paths and then disable the option "Settings -> Debugger -> auto build project if it is not up to data"
so, now I'm done whining & actually doing what you've suggested it works. and it works sweet.
this is why this is frustrating. you've done the hard bit. just a little "icing on top" & that's another weird quirk transformed into another awesome feature. :)
Other stuff:
Editor shortcut config & incremental search should be standard base package features not addons imo.
Not suggesting changing your default key bindings. Your choice there is more intuitive but allowing secondary binding packages (or however you want to call it) to provide shortcuts that match other popular packages would aid user migration.
Cheers guys.
oBFusCATed:
--- Quote from: advance-software on June 18, 2013, 02:32:45 pm ---...a more intuitive interface will make support easier and the product better.
--- End quote ---
C::B is not a product in the common sense, but free software project/tool.
Adding features makes one software harder to maintain/support.
--- Quote from: advance-software on June 18, 2013, 02:32:45 pm ---Editor shortcut config & incremental search should be standard base package features not addons imo.
--- End quote ---
Here I agree.
--- Quote from: advance-software on June 18, 2013, 02:32:45 pm ---Not suggesting changing your default key bindings. Your choice there is more intuitive but allowing secondary binding packages (or however you want to call it) to provide shortcuts that match other popular packages would aid user migration.
--- End quote ---
Key collisions are inevitable...
advance-software:
> Key collisions are inevitable...
Sorry, phrased that badly. Key mapping templates. Either standard CB or standard VC or whatever, which could then be customized by users & saved as their bindings defaults. Again, sounds like you have most of this already. Just the option of being able to select VC bindings & that one's done.
But here I'll come onto your side of the fence & say these things are fluff that aren't hard to deal with once you know the system.
Of more importance is there's still a little debugging weirdness. Get the occasional lockup. No idea if it's CB or gdb. Update when I have more info,
advance-software:
Ok, back to the using codeblocks as a debugger front end feature :
If I untick settings -> Debugger -> auto build project if not up to date as advised ...
... the properties, build targets execution working directory is ignored & the app starts from the directory that the project would have built into had I not unticked auto build (hope that makes sense)
I want to be able to step into an existing executable & specify the startup directory.
Will go back to ddd for this for now as too many obscure hoops to jump through in cb right now but a shame this isn't closed out in an intuitive manner ... would make the product a lot more useful & you're so close to having an awesome new feature.
Understand the resource issue. Sorry, overloaded too right now & no beer tokens with which to compensate you at the moment.
Working on that ... might even happen one day :)
BlueHazzard:
--- Quote from: advance-software on June 19, 2013, 07:18:01 pm ---I want to be able to step into an existing executable & specify the startup directory.
--- End quote ---
i think this should help:
Project->Properties->Build Targets->Execution working dir
--- Quote from: advance-software on June 18, 2013, 02:32:45 pm ---"Settings -> Debugger -> auto build project is a global setting so I'd have to remember to switch this on/off as I switch projects. That might work but it's not a good solution.
--- End quote ---
I think too that this should be a project specific setting...
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version