python-visual + python2.6 crashed with SIGSEGV in __cxa_allocate_exception(). python command was 'from visual import *

[ez2023]

Binary package hint: python-visual

newly installed karmic alpha 5.
command sequence to crash

as root:
aptitude update
aptitude install python-visual

as user

$ python
Python 2.6.2+ (release26-maint, Jul 24 2009, 16:16:12)
[GCC 4.4.1] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from visual import *
Segmentation fault (core dumped)
$

ProblemType: Crash
Architecture: i386
Date: Thu Sep 3 13:24:56 2009
Dependencies:
 findutils 4.4.2-1
 gcc-4.4-base 4.4.1-3ubuntu3
 libc6 2.10.1-0ubuntu8
 libgcc1 1:4.4.1-3ubuntu3
 zlib1g 1:1.2.3.3.dfsg-13ubuntu1
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/python2.6
Package: python2.6-minimal 2.6.2-0ubuntu3
ProcCmdline: python
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-9.29-generic
SegvAnalysis:
 Segfault happened at: 0x1985bc7 <__cxa_allocate_exception+55>: addl $0x1,0x4(%eax)
 PC (0x01985bc7) ok
 source "$0x1" ok
 destination "0x4(%eax)" (0x0000000c) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: python2.6
StacktraceTop:
 __cxa_allocate_exception () from /usr/lib/libstdc++.so.6
 boost::python::throw_error_already_set() ()
 boost::python::objects::class_base::add_static_property(char const*, boost::python::api::object const&, boost::python::api::object const&)
 ?? () from /usr/lib/python2.6/dist-packages/cvisualmodule.so
 ?? () from /usr/lib/python2.6/dist-packages/cvisualmodule.so
Title: python2.6 crashed with SIGSEGV in __cxa_allocate_exception()
Uname: Linux 2.6.31-9-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #408663, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.