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

How to watch wxString under OSX from CodeBlocks and GDB ?

<< < (2/3) > >>

oBFusCATed:

--- Quote from: eranon on February 15, 2013, 06:34:26 pm ---It would be the easiest and quickest, of course. Do you know one ?

--- End quote ---
Yes, every major linux has one, for me macosx is something I want to stay away as much and as far as possible.

wx2.9 rewrote the string class, so the internals are very different and need newer scripts.

eranon:

--- Quote from: oBFusCATed on February 15, 2013, 06:50:56 pm ---Yes, every major linux has one, for me macosx is something I want to stay away as much and as far as possible.

--- End quote ---
Outside of OSX, of course, there're ;) But, obviously, I told about one which runs under OSX... However, originally, I'm like you (far away from Mac), but I can't forget it (no choice and it's the main part of my decision to go the cross-platform and wxWidgets way) just because there're a lot of Mac users in the field where my app will be released ::)


--- Quote from: oBFusCATed on February 15, 2013, 06:50:56 pm ---wx2.9 rewrote the string class, so the internals are very different and need newer scripts.

--- End quote ---
On C::B side, I guess its the script called "gdb_types.script" under "src/plugins" in SVN repo. I see it's written by MortenMacFly... Hello Morten :) Do you plan to update it for wx 2.9 ? ;D Or do you wait for wx 3.x :o

oBFusCATed:

--- Quote from: eranon on February 15, 2013, 07:27:00 pm ---On C::B side, I guess its the script called "gdb_types.script" under "src/plugins" in SVN repo. I see it's written by MortenMacFly... Hello Morten :) Do you plan to update it for wx 2.9 ? ;D Or do you wait for wx 3.x :o

--- End quote ---
This script is something from the past. There are no plans to further improve it.

See this: http://doc.qt.digia.com/qtcreator/creator-debugger-engines.html

eranon:
I agree about the fact a Python-enabled debugger would be the best way. In the page you pointed for me (thanks), I read (and I guess its the info you wanted I see) there's currently and experimental and unstable Python-enabled GDB for OSX around (the FSF GDB). Well, all depends of the level of unstability (i.e. what to avoid to do during a debugging session).

--
EDIT : Finally taken a try building current FSF GDB from Git repository, then codesigned it against a new certificate. Now it shows the wxString (not on a single ligne, but doesn't matter : it displays the structure and I can navigate to see useful data), but I can't always do what I want about breakpoints, steps, and sometimes I can't stop it (I have to close C::B)... Well, so, not sure at this step what to do : go on with erratic FSF GDB or use Apple-restricted GDB w/o full watching feature... Well, well ::)

eranon:
up

Still in trouble with gdb under OSX from within Codeblocks. Well,

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 ?

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 ?

Navigation

[0] Message Index

[#] Next page

[*] Previous page