User forums > Help
Pretty Printers working only for global variables
oBFusCATed:
One way to check if gdb's pretty printers are working is to stop at a breakpoint, switch to the debugger's log and execute the "info pretty-printer" command. It should list your pretty printers that are currently active. Also another command you can try is "print myVector" to see the raw output of gdb.
ollydbg:
--- Quote from: Sab on May 17, 2015, 01:35:44 pm ---I have only one GDB. I have attached my settings->compiler->toolchain config.
my current stl.gdb file
--- Code: ---python
import sys
sys.path.insert(0, 'C:\MinGW\share\gcc-4.9.2\python')
from libstdcxx.v6.printers import register_libstdcxx_printers
end
--- End code ---
after this I am not getting any error in C::B debugger prompt but still pretty printers are not working in C:B while in command prompt it is working.
--- End quote ---
I want to see the "full debugger log" when the problem you mentioned in the first post happens. I mean the log message when you have problems in shown in yy.png.
Sab:
--- Quote from: ollydbg on May 17, 2015, 03:15:04 pm ---I want to see the "full debugger log" when the problem you mentioned in the first post happens. I mean the log message when you have problems in shown in yy.png.
--- End quote ---
I have attached the files debugger-first.txt is the first one and debugger-now.txt is the current one.
first config : as present in the first post screenshots and stl.gdb:
--- Code: ---python
import sys
sys.path.insert(0, '')
from libstdcxx.v6.printers import register_libstdcxx_printers
register_libstdcxx_printers (None)
end
--- End code ---
path to stl.gdb - C:\MinGW\bin\stl.gdb
sorry for the bad attachment name in my first post.
I tried re-installing code :: block still no use. MinGW I currently have - x86_64-4.9.2-release-posix-seh-rt_v4-rev2
ollydbg:
Hi, Sab.
I looked the two txt files.
debuglog-now.txt looks correct, and debuglog-first.txt is wrong. Because I see
--- Code: ---Registered new type: wxString
Registered new type: STL String
Registered new type: STL Vector
--- End code ---
which means you did not turn off the watch script in debuglog-first.txt.
But I don't see the variables like "m, v, q, s" in the debuglog-now.txt, so what is the problem right now?
Sab:
Sorry, I thought u wanted the gdb starting log, I have attached the one with print command
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version