User forums > Nightly builds
The 17 May 2012 build (7966) is out.
MortenMacFly:
--- Quote from: oBFusCATed on May 30, 2012, 09:19:58 am ---Yes, it is known issue...
--- End quote ---
Yes, I noticed that, too. We should try to find a solution for that. IMHO its related to the PipedProcess class but this is hard to track and (as we found out many times) a sensitive component. My suggestion would be to introduce an own "PipedProcess" class better suited for the debugger not affecting any other components.
@oBFusCATed would that be a "good thing to do" [tm]?
oBFusCATed:
The general slowness comes from the fact that every line of output generates a wx event, which is quite slow.
The previous attempt failed rather miserably, so I'm not sure I want to invest time in improving the situation.
I have very little free time at the moment, because I've started to write my Bachelor's thesis (or whatever is the name in English), so the next two-three mouths will be quite busy.
The GDB/MI plugin doesn't have this problem, because there are less lines of output. Every result from a command is a single line. But unfortunately it is not ready. :)
ollydbg:
--- Quote from: oBFusCATed on May 30, 2012, 12:02:19 pm ---The general slowness comes from the fact that every line of output generates a wx event, which is quite slow.
The previous attempt failed rather miserably, so I'm not sure I want to invest time in improving the situation.
I have very little free time at the moment, because I've started to write my Bachelor's thesis (or whatever is the name in English), so the next two-three mouths will be quite busy.
--- End quote ---
Congratulation!
It looks like you are much younger than me. :)
--- Quote ---The GDB/MI plugin doesn't have this problem, because there are less lines of output. Every result from a command is a single line. But unfortunately it is not ready. :)
--- End quote ---
What has left in GDB/MI?
@hooluupog
Can you post the steps in both GDB command line and Codeblocks log, also the source code. I'm going to test the lag. Thanks.
oBFusCATed:
--- Quote from: ollydbg on May 30, 2012, 01:48:35 pm ---Congratulation!
It looks like you are much younger than me. :)
--- End quote ---
Not that young, I've used the whole available period of 5 years for postponing it :)
--- Quote from: ollydbg on May 30, 2012, 01:48:35 pm ---What has left in GDB/MI?
--- End quote ---
Polishing...
--- Quote from: ollydbg on May 30, 2012, 01:48:35 pm ---@hooluupog
Can you post the steps in both GDB command line and Codeblocks log, also the source code. I'm going to test the lag. Thanks.
--- End quote ---
Create an array with 10000 elements and try to watch it, should trigger the bug.
If it doesn't trigger it, try array with 10000 wxstring or std::string elements :)
Another way to test it to add 10-20 big classes (many members in them) in the watch window.
hooluupog:
--- Quote from: ollydbg on May 30, 2012, 01:48:35 pm ---]
@hooluupog
Can you post the steps in both GDB command line and Codeblocks log, also the source code. I'm going to test the lag. Thanks.
--- End quote ---
The source code and codeblock's log are in attachment.
The steps of GDB command line:
(gdb)file main.exe
(gdb)set print elements 0
(gdb) source c:/minGW32/bin/.gdbinit
(gdb) b 8
(gdb)b 15
(gdb)r
(gdb)c
(gdb)p s
(gdb)p in
[attachment deleted by admin]
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version