[Freewx-maint] Bug#746526: python-wxgtk2.8: python segfaults on wx/_html.so

Olly Betts olly at survex.com
Thu Aug 7 06:14:40 UTC 2014

On Thu, May 01, 2014 at 12:17:03AM +0100, Olly Betts wrote:
> On Thu, May 01, 2014 at 12:49:53AM +0200, Martijn wrote:
> > I encountered segfaults of python2.7 when using wikidpad. Running it through
> > gdb revealed that the problem was wx/_html.so:
> > At the moment of  the crash I had the wikidpad internal html rendere switched
> > on en was browsing the wiki.
> > After I disabled html rendering or swithed to the webkit renderer, which is
> > offered in addition to the wxwidget html widget, wikidpad ran without problems.
> > This pinpoints the problem to the wxwidget html engine or underlying modules.
> > 
> > The gdb listing prior after the segfault is:
> > 
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x00007ffff4b02b07 in wxArrayString::Index(wchar_t const*, bool, bool) const ()
> > from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
> > (gdb) pyframe
> > No symbol "PyStringObject" in current context.
> > (gdb) up
> > #1  0x00007ffff5b2ff74 in wxHtmlTag::HasParam(wxString const&) const () from
> > /usr/lib/x86_64-linux-gnu/libwx_gtk2u_html-2.8.so.0
> Without debug info, this doesn't really help narrow things down enough.
> You could retry with python-wxgtk2.8-dbg instead of python-wxgtk2.8 -
> despite the name, it's actually a replacement build rather than just
> detached debug symbols (because it predates the -dbg naming convention).
> Unfortunately, wx 2.8 is effectively no longer maintained.  Upstream
> haven't officially ended development, but nobody actually willing to put
> in the work to continuing making 2.8.x releases has stepped forward in
> the ~3 years since 2.8.12 was released, and bug reports against it
> rarely get much attention.
> I'm working on moving Debian to wx 3.0, but I haven't packaged wxpython
> 3.0 yet.

wxpython3.0 is now available in unstable - if you are able to retest
with that and the problem still occurs, we can report it upstream and
it may get fixed.


More information about the Freewx-maint mailing list