Author Topic: someone working on CDB debugger?  (Read 48753 times)

Offline Martin K.

  • Multiple posting newcomer
  • *
  • Posts: 86
Re: someone working on CDB debugger?
« Reply #30 on: October 11, 2012, 08:39:26 pm »
Any Ideas?
Hopefully oBFusCATed can say something more detailed about this, but weren't there just with the last commits some changes accordingly to fix a  (similar/same) wrong behaviour accordingly? Are your sources in sync with trunk?

yes, my sources are compiling fine to the trunk.

Martin

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12086
    • Travis build status
Re: someone working on CDB debugger?
« Reply #31 on: October 11, 2012, 09:18:19 pm »
ShiftBreakpoint function should re-set the breakpoint only if the compiler supports edit-and-continue, but c::b currently doesn't support edit-and-continue.
I'm not sure what is the best action we could take. The options are:
1. Mark the breakpoint as invalid (should provide some api for it)
2. Don't move the breakpoints and tell the editor that the must stay at the same line as before the edit operation, thus the breakpoint and the source will diverge.
3. Anything else...
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline Martin K.

  • Multiple posting newcomer
  • *
  • Posts: 86
Re: someone working on CDB debugger?
« Reply #32 on: October 11, 2012, 11:04:48 pm »
OK,

i do what M$ does, what the best solution is - maybe. Warn the user about the changes, update the editor marks and let the debugger run into the wrong breakpoint position.

Martin

BTW: I like to have the possibility to load a source file into the editor, which is not known to the project. Why? For example, i have installed wxWidgets from wxPack. my path for the installation is c:\codeblocks\wxWidgets2.8.12. When i debug an application and break (or step) into the wxWidgets library, than CDB gives me symbols for the original path where the library was build from by someone who builds wxPack. My project has never build the library and my paths are not the same a those be used from the wxPack team. So i like to open source files like the WinDbg debugger will open it, or i like to let the user define some type of replace-mask, so that he (or i :-) can step into the library source (or any other source) without having them to be in the same path as the library creator. Any suggestions on this? SyncEditor calls always the project file functions.

thanks Martin


Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12086
    • Travis build status
Re: someone working on CDB debugger?
« Reply #33 on: October 11, 2012, 11:53:15 pm »
SyncEditor calls always the project file functions.
As far as I can see it should work if you pass the correct path to the file on your system. Have you tried it?
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline Martin K.

  • Multiple posting newcomer
  • *
  • Posts: 86
Re: someone working on CDB debugger?
« Reply #34 on: October 12, 2012, 12:26:20 am »
SyncEditor calls always the project file functions.
As far as I can see it should work if you pass the correct path to the file on your system. Have you tried it?

no, i have not tried it, i have had only a look at the source code - too many construction sites...
I will try it next week, because i am on a short vacation this weekend (vienna).

Martin

Offline Martin K.

  • Multiple posting newcomer
  • *
  • Posts: 86
Re: someone working on CDB debugger?
« Reply #35 on: October 19, 2012, 06:28:15 pm »
The next, rev 10:

- in sync with Code::Blocks rev8462
- added Windows Version resource
- show backtrace/callstack with function arguments
- disassembly for code without source
- better handling of disassemble view updates (still not completed but not bad)
- additional debugger commandline args in the configuration
- some cosmetic changes

Martin

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9508
Re: someone working on CDB debugger?
« Reply #36 on: October 19, 2012, 08:50:24 pm »
The next, rev 10:
- [...long list...]
Sounds pretty amazing. Maybe after all that time I should give CDB another try...
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline Martin K.

  • Multiple posting newcomer
  • *
  • Posts: 86
Re: someone working on CDB debugger?
« Reply #37 on: October 19, 2012, 10:28:57 pm »
just try it. I think that it already runs better as the current plugin, but this is only my meaning currently. Every found problem is one problem less. And the visual c++ compiler is much faster on windows as gcc.
When this plugin works - and the gdb/MI plugin also - than you can switch completely to the "new" debugger plugin api.

Martin


Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12086
    • Travis build status
Re: someone working on CDB debugger?
« Reply #38 on: October 19, 2012, 11:50:09 pm »
I don't understand your last comment, as we have already switched to the new debugger plugin api.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline Martin K.

  • Multiple posting newcomer
  • *
  • Posts: 86
Re: someone working on CDB debugger?
« Reply #39 on: October 20, 2012, 09:46:23 am »
I don't understand your last comment, as we have already switched to the new debugger plugin api.

Sorry, my english is not the best. The current debuggers depend on each other so much, that i couldn't remove one of them.

Martin

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9508
Re: someone working on CDB debugger?
« Reply #40 on: October 20, 2012, 12:32:48 pm »
I don't understand your last comment, as we have already switched to the new debugger plugin api.
I think he means the GDB/MI plugin... which I would indeed like to switch to when you say its ready. :-)
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline Martin K.

  • Multiple posting newcomer
  • *
  • Posts: 86
Re: someone working on CDB debugger?
« Reply #41 on: October 22, 2012, 06:41:19 pm »
rev 11:

- fixed an error with the destruction of tooltip watches
- fixed a race condition on closing code::blocks while staying in the debugger
- added "set next statement" function
- added the ability to map symbol paths to local source paths
- added "start step into"

Martin

Offline Martin K.

  • Multiple posting newcomer
  • *
  • Posts: 86
Re: someone working on CDB debugger?
« Reply #42 on: October 24, 2012, 02:04:17 pm »
Hi,

I have seen that the DisassemblyDialog is very slow. Adding 4800 assembler lines take 10 seconds (4800 lines is 250 c++ lines generated from wxSmith). Any change to speed it up a little bit?

Martin

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 12086
    • Travis build status
Re: someone working on CDB debugger?
« Reply #43 on: October 24, 2012, 02:45:59 pm »
Patches welcome:)
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline Martin K.

  • Multiple posting newcomer
  • *
  • Posts: 86
Re: someone working on CDB debugger?
« Reply #44 on: October 24, 2012, 03:01:10 pm »
Patches welcome:)

:-)

OK, it goes into my list.

Martin