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

How to watch wxString under OSX from CodeBlocks and GDB ?

<< < (3/3)

oBFusCATed:

--- Quote from: eranon on February 06, 2014, 07:58:10 pm ---1) If I use the Apple-flavor of gdb, I have no Python support and can just check the "Enable watch scripts" ("Watch local variable" being pre-enabled and greyed)... But it doesn't show anything during debugging (knowing, talking about a wxWidgets-based project, I can at least see a wxString structure like a raw tree using this same gdb from command line). So, if I refer to this old thread, chance the underlying script be broken. Is there a plan to update it ?

--- End quote ---
No, the only change I'll do about it in the future is to remove it. There is no point in wasting time, because it is slow, hard to extend and unreliable.


--- Quote ---2) If I use a Python-enabled FSF gdb, it seems I fall in an incompatibility with the binaries produced by the Apple LLVM GCC 4.2 shipped with the Xcode tools (an info coming from the FSF gdb mailing-list where I've asked). So, is there another Python ebaled gdb which would be LLVM GCC 4.2 compliant and supported by Codeblocks ?

--- End quote ---
I'm no mac user, so I can't help much. Probably in the future someone will find the time to write a lldb debugger plugin for codeblocks, apple has abandoned the fsf toolchain, so I won't expect any improvements in gcc/gdb in the future.

eranon:
Well, it's what I was afraid about :-\ Thanks for this point, Obfuscated, but, then, the question is : How do the ones who are using Code::Blocks under OS X ? If there are some Mac-men around, I would be very interested to hear them (for sure).

oBFusCATed:
We need someone using OSX and willing to invest time improving C::B on it. Until then the situation won't improve much. Sorry.

eranon:
I understand. I discover myself everyday the black-box that OSX is and frankly if I had the choice I would stay away.. Hoping you'll find a Mac dev soon ;)

eranon:
Final point (if it can help someone), all of this under OS X 10.8.3 Mountain Lion :

As I said in a previous post above, I needed a Python-enabled debugger and the Apple LLVM-GDB is not, So, I installed a FSF-GDB (6.3 from Homebrew), but it was incompatible with the binaries produced by LLVM-GCC (4.2)... Then, I installed a FSF-GCC (4.7), but for a reason I don't succeed to define, it was wrong too with these new binaries (weird!). Nevertheless this step was not useless since I got ride of the GCC's Apple-flavor and decided to keep the true FSF one (as under MSW I don't use MSVC but MinGW-GCC).

GDB (both LLVM and FSF) being eliminated, I taken a try with the LLDB shipped with Xcode (4.6), and it worked with my binaries coming from FSF-GCC) Next step was to install the last current LLDB (ie. from SVN HEAD) and to find a good front-end : the choice being very poor, I tried the current beta of Affinic Debugger GUI and it works fine (at least with the LLDB 300.x I have now). Next step will be to manage at Python-side to be able to watch wxWidgets's structures (e.g. about wxString, seen this http://stackoverflow.com/questions/12923873/how-to-print-wchar-t-string-in-lldb).

Of course, not to say that all of this is a solution awaiting a LLDB plugin for Code::Blocks ;D

--
EDIT : since I opened a similar thread on the wx forum, I duplicate this final post over there too.

Navigation

[0] Message Index

[*] Previous page