GDB Python support

Bryce Schober
Thu Mar 17 17:30:00 GMT 2011

So I've burned several calories on this, and basically haven't gotten
anywhere. Apparently, GDB's python "integration" doesn't like the
lib/include layout on Ubuntu (don't most do it that way?), so it can't
handle my pre-existing python without some patching that I wouldn't
want to get into. I did run the Linux build from successfully. I
was hoping that I'd be able to figure out how to adapt the necessary
bits of what they're doing into crosstool for a cross toolchain, but I
fear I'm not qualified. And FWIW, it looks like actually building
python is pretty trivial, and probably wouldn't be that huge a deal to
do in crosstool itself.

<><  <><  <><
Bryce Schober

On Tue, Mar 15, 2011 at 11:47 AM, Yann E. MORIN
<> wrote:
> On Tuesday 15 March 2011 02:10:55 Bryce Schober wrote:
>> This is what I mean. It requires specifying gdb's configure option
>> "—with-python" (my cursory glance at crosstool's configs left me with
>> the impression that there was no place to plug in that option),
> There is currently no way to add user-supplied options to gdb's
> ./configure.
> Here is attached a untested patch. Care to report, please?
> There are two places to enable python support:
> - for the cross-gdb: we can use the python available on the host
> - the native gdb: it is a bit more complex, as it requires an existing
>  python to run on the target, *and* an exiting python devel env to run
>  on the target. Obviously, we can't readily have this target python,
>  as we're still building the toolchain. And, no-no-no, I won't add a
>  python devel env in the toolchain.
> So, for the native gdb to run on the target:
> - either it does not support python scripting,
> - or the user will have to build it on his/her own.
>> and
>> implies dependencies. I assume that in the context of crosstool, one
>> would prefer it to compile its own minimal version of python for that
>> purpose. I haven't gone very far down the chain of implications
>> myself, but I've scanned through the Qt Creator process for the
>> python-enabled gdb that they ship
>> (, and at least
>> their Linux build process doesn't look too obtuse.
> For the cross-gdb, we can assume that the host laready has the python devel
> env (headers+libs). For the native gdb, that's a no-no in crostool-NG.
> Regards,
> Yann E. MORIN.
> --
> .-----------------.--------------------.------------------.--------------------.
> |  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
> | +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
> | +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
> | | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
> '------------------------------^-------^------------------^--------------------'
> --
> For unsubscribe information see

For unsubscribe information see

More information about the crossgcc mailing list