Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Splitting debugger in two - specific debugger and common GUI
oBFusCATed:
Because scintilla on windows is not sending the dwell start event if the control or other key is pressed.
I don't know why it doesn't happen on linux, but I see no side effects here. Time will tell.
This is the discussion of Ollydbg with one of the Scintilla devs: http://groups.google.com/group/scintilla-interest/browse_thread/thread/7d109d6e9c6a18f5/700a7871969920da?lnk=gst&q=dwell#700a7871969920da
p.s. there seem to be more problems with the gdb 7.3...
oBFusCATed:
--- Quote from: dmoore on August 12, 2011, 05:38:15 pm ---On Topic: I should probably just read the thread/code, but do you have a cliff notes version of the status of your work on the debugger API, oBFus? (May have some free time to think about the python debugger again in coming months)
--- End quote ---
dmoore (and others of course):
I've almost finished the switch from raw pointer/references to cb::shared_ptr, only the watches are to be converted (will do it this week, hopefully).
Can you look at the API for some missing bits are things that you don't like?
After I'm finished with the watches I plan to add 'Supported features API', so different plugins can advertise what they support or doesn't support.
dmoore:
oBFusCATed: That sounds good. I wil try to take a look in the next couple of weeks. Unfortunately, v.busy atm.
tomjnx:
ParseOutput expects to get debugger output line-wise - however the cbTextInputStream does not really guarantee ReadLine to always return a full line. Not being able to read does not mean we are at the end of a line, it could also be that the sending process hasn't written the remainder of the line or the operating system hasn't caught up getting everything to the receiving process. I haven't seen this problem under linux, but on quite a few windows machines it happens occasionally.
If we can no longer read but haven't seen an EOL, we need to buffer the already read characters, return an empty line, and continue on the next call. The attached patch fixes the problem for me.
oBFusCATed:
Hm, OK, I'll give it a try, but I'm mostly on windows.
Edit: replace windows with linux...
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version