User forums > Nightly builds

The 06 July 2014 build (9844) is out.

<< < (4/4)

BrianSidebotham:

--- Quote from: oBFusCATed on July 28, 2014, 09:39:12 pm ---
--- Quote from: BrianSidebotham on July 25, 2014, 12:12:16 pm ---I'm having trouble with "Project->Properties->Debugger->Additional shell commands->Before connection"

--- End quote ---
I think this is know problem I have to find time to fix.

--- End quote ---

Excellent, no problem then.


--- Quote from: oBFusCATed on July 28, 2014, 09:39:12 pm ---
--- Quote from: BrianSidebotham on July 25, 2014, 03:17:09 pm ---Also it appears that breakpoints don't get removed when using remote debugging. I tried just removing them from the scintilla gutter and also using "Remove All" from the breakpoints window, but nothing clears the breakpoints.

--- End quote ---
Can you post the full log from the debugger (you have to enable it in the settings).
Can you reproduce the problem with simple console project and gdbserver run on a PC, not some embedded device?

--- End quote ---

Some further information:

(1) This only happens for remote debugging, debugging the same target on Windows in the same fashion works fine.

(2) Only breakpoints that are created offline, or in other words before debugging is started cannot be removed. On Windows when I set a breakpoint in the code and then start debugging, if I remove that breakpoint I see the command: [debug]> delete breakpoints 3. Under remote debugging the breakpoint gutter icon is removed, but I don't see any command produced in the GDB session.

I hope that makes sense, it's easier than giving a noisy log of GDB activity. Let me know if there's any more information I can provide for you.

Best Regards, Brian.

oBFusCATed:
Have you tried to reproduce the problems with running remote debugging against gdbserver started on a windows pc. I think it is possible and this is the only way I can reproduce them and probably fix them.

ollydbg:

--- Quote from: oBFusCATed on July 31, 2014, 09:38:19 am ---@Alpha: Do you know why it is asking to set the default compiler? It happens after an upgrade from 9848 to 9853...

--- End quote ---
I also have this issue when I update to 9854 nightly.

Alpha:
Oops, missed that question :-[ .  If I correctly remember, that dialog is triggered whenever batch compiler autodection is run (e.g. some compiler(s) are registered without previous existence in the conf file).  The intent there was that these new compiler settings could potentially be incorrect (due to automatic algorithms), so alerting the user of changes is probably best.

I will have to check back into the code later for further details...

oBFusCATed:
Makes a bit of sense, but there is no explanation why this happens presented to the user or at least it is not clear enough. So we as users get confused/annoyed quite a lot.

Navigation

[0] Message Index

[*] Previous page