The advice lead me to the solution.
In the debug log you can execute the command "info pretty-printer". It will show you some output or an error.
Thanks a lot, oFBfusCATed -> you made my day
.
So the procedure I followed was correct.
It showed me that I had been looking at the wrong end. Most of the versions I tried actually were python
enabled and worked fine with pretty-printing itself. Just I did not recognise. The problem was in my
manual script change in "
http://qp-gcc.googlecode.com/files/stdcxx_and_wx_pythonscript.7z". The change
itself was syntactically correct but obviously I used a TAB somewhere. I just learned that python seems
to be pretty allergic against tabs - quite a surprise. I remove any tabs and, voila, my wxString content
printouts were there, wether or not _T("..") or "..".
So I learned for my procedure :
- check if the gdb base is ok: Run debug, enter in its command line "info pretty-printer". If you get
' Undefined info command: "pretty-printer".', you need another gdb or python or you would'nt see
a wxString output.
- Enable Settings/Debugger/Full log and look at the line where the source commands are executed.
The OK output shoudl be '>>>>>>cb_gdb:>>>>>>cb_gdb:'
- Only if both is OK, start looking at the syntax in the scripts
Now, I have two more things:
1) am intertested in thoughts on the following approach:
I have to use different version of gcc in some cases. Thus I install my compilers not in the C::B directory
but on the same level as C::B itself. I found that seems to work for the debugger as well. I just did
the setup today and need to work a bit still to see any side effects. Maybe someone else is already
working with that setup.
The setup looks like this
C:/
CodeBlocks/
Gdb_wxUnicode/
bin/
libstdcxx/
libwx/
include/
share/
Gdb_beforeUnicode/
MinGw4.62/
MinGw5.3/
MinGw64bit
The gdb bin only has a gdb.exe and a gdbserver.exe and the printer scripts including their subdirs. I was a
bit surprised that it does not require more resources of the MinGw directory, but so far works fine. The very
nice thing is that I can switch between gdb setups by only editing the C::B/Settings/Debugger/Default/
ExecutablePath. I could install/deinstall MinGw without the need to touch gdb again.
Maybe I overlooked something?
2) I think it would be nice to have an updated Zip file with that fully working setup. A python enabled gdb
and the script files with the changes (but without python installer) for convenience of others (an myself
in the future) with a link it in the post. I do not have any cloud space and also wouldn't think its good
to put it somewhere where the link dies when the provide company decide its time to change their
business model. There are too many dead links to interesting stuff in other forums I use. If someone
is willing to help me finding a place where to put it I can offer to prepare the package with instructions.
Maybe there is even a newer python enabled gdb than 23.05.2014. I did not find any links or hints
to the pything enabled gdbs on the MinGw website, but I probably just missed then.
Cheers,
Tiger
