Re: [rox-users] Rox now totally inoperative

[Thomas L. <ta...@gm...>]

On 4/24/07, Mike Hobbs <mik...@an...> wrote:
> In message <f0famq$53m$1...@se...>
>           Thomas Leonard <ta...@gm...> wrote:
>
> > On Mon, 16 Apr 2007 14:29:41 +0100, Mike Hobbs wrote:
> >
> >> Ah, found it - well, another app failed with the same message
> >> and I recognized it:
> >> python: Objects/stringobject.c:110: PyString_FromString: Assertion
> >> `str != ((void *)0)' failed.

> I'm no expert on Python but whenever I've developed apps using
> Python it gives traceback info allowing you to see where
> execution was when something went wrong. However, in the above
> case there is no traceback. Has it been suppressed somehow?
> Can it be turned on?

The bug is in C code rather than Python, but you can get a C backtrace
easily enough using gdb:

$ gdb python
(gdb) run .../prog.py

(then wait for the crash)

(gdb) backtrace

If you get a load of "?? ()" lines then you're running a version
without debug symbols. The backtrace might still contain useful
information though.

You can get a more verbose list with:

(gdb) backtrace full


-- 
Dr Thomas Leonard		http://rox.sourceforge.net
GPG: 9242 9807 C985 3C07 44A6  8B9A AE07 8280 59A5 3CC1