User forums > General (but related to Code::Blocks)

[OT] unofficial MinGW GDB gdb with python released

<< < (26/35) > >>

MindVortex:
Thank you anyhow! I'll see what I can do.

nenin:

--- Quote from: ollydbg on August 10, 2011, 04:19:45 am ---BUMP:
the 2011-08-10 version just has auto-loaded gdb's own python script support for pretty-printer. see
[OT] unofficial MinGW GDB gdb with python released for more details.  :D

--- End quote ---

It works ... but I found odd thing: sometimes gdb crashed on start. Looks like it try to prepare non-initialized local variables in main for pretty-printing. At least switch off corresponding option in Setting results in stable (and really fast) further operation.

ollydbg:

--- Quote from: nenin on August 17, 2011, 05:34:52 pm ---It works ... but I found odd thing: sometimes gdb crashed on start. Looks like it try to prepare non-initialized local variables in main for pretty-printing. At least switch off corresponding option in Setting results in stable (and really fast) further operation.

--- End quote ---
Did you mean like below:

--- Code: ---int main()
{
int a;// set breakpoint here

vector<string> b;

}

--- End code ---
Then, you try to use pretty printer to show the variable b?
surely, b is non-initialized local variable, and this will let gdb/python script go to some un-expected behavior, like go infinite loop to show its member.

This is a known bug, I have discussed this bug in this forum before. I also have a workaround patch on GDB to compare the line number between the current PC address and the variable line, then try to filter out the non-initialized local variable. But I do not think this patch will be much reliable.

nenin:

--- Quote from: ollydbg on August 18, 2011, 03:16:55 am ---Did you mean like below:

--- Code: ---int main()
{
int a;// set breakpoint here

vector<string> b;

}

--- End code ---
Then, you try to use pretty printer to show the variable b?
surely, b is non-initialized local variable, and this will let gdb/python script go to some un-expected behavior, like go infinite loop to show its member.

--- End quote ---
I did not. But C::B did it by default, in "Local variables" section of watch.

ollydbg:

--- Quote from: nenin on August 18, 2011, 12:37:31 pm ---I did not. But C::B did it by default, in "Local variables" section of watch.

--- End quote ---
En, that's the same thing I said in my previous post.

Navigation

[0] Message Index

[#] Next page

[*] Previous page