Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development

someone working on CDB debugger?

<< < (2/12) > >>

oBFusCATed:
Hm, interesting...
I didn't know that there is this kind of a dll.
So the best way is to write a new debugger engine application as MS call it, which can use some IPC mechanism to communicate with a debugger plugin.
Another option is to try to integrate the dll in a new debugger plugin.
This way you won't need to parse the text output from CDB, which is close to unparsable sometimes.

Martin K.:
Hi,

OK, i'm working on this and have one first Question:
In ExamineMemoryDlg::AddHexByte there is a loop for 16 hex bytes in one row of the window. But m_LastRowStartingAddress will be advanced by only 8. Is this OK?

Martin

oBFusCATed:
I'm not sure. Have you look what is the output of the gdb that is being parsed?
Keep in mind that the examine memory window has not been made generic,
it simply has been extracted from the code inside the plugin to the sdk without modifications.
It is very gdb specific and needs some work to be made generic.

Martin K.:
Hi,

I have found "my" Problem. The fault is inside of  ExamineMemoryDlg::AddHexByte();

It takes the address of the memory range to be displayed once on the first value, and then after every completed line. There are a maximum of 16 Values in each line and the next address will be computed from the last adress value + 8. This works only when the adress delivered to this funktion will is valid on every 8. value and don't change for the next 8 values.
The GDB Driver will work, it "sends" the memory dump values to this funktion in packages of 8 values. Every other combination will not work. And there is an additional Problem when the memory dump starts at address 0.

I will work around this problem in my funktion until someone other fixes the behaviour of  ExamineMemoryDlg::AddHexByte().

Martin

oBFusCATed:

--- Quote from: Martin K. on October 01, 2012, 12:39:27 pm ---I will work around this problem in my funktion until someone other fixes the behaviour of  ExamineMemoryDlg::AddHexByte().

--- End quote ---
Why not fixing the AddHexByte directly?

Navigation

[0] Message Index

[#] Next page

[*] Previous page