[C++-sig] segmentation fault when executing PyImport_ImportModule("sys")

Dietrich Bollmann diresu at web.de
Sat Apr 12 15:46:45 CEST 2008


Hi Venkatraman S,

Thanks for you answer:

On Tue, 2008-04-08 at 19:59 +0530, Venkatraman S wrote:
> 
> 
> On Tue, Apr 8, 2008 at 4:01 PM, Dietrich Bollmann
> <d.bollmann at tu-berlin.de> wrote:
>         Program received signal SIGSEGV, Segmentation fault.
>         [Switching to Thread 0xb046ab90 (LWP 9854)]
>         threadstate_getframe (self=0xb7e8a889)
>         at ../Python/pystate.c:154
>         154     ../Python/pystate.c: No such file or directory.
>                in ../Python/pystate.c
> 
> Am not sure whether i get the context right - but i was stumbling on 
> a similar SIGSERV in a multithreaded app - profiling with Valgrind 
> turned out to be much useful and the memory leak was fixed.

I already had found the right trace and didn't need Valgrind anymore.
(if you are interested, here is the solution to my problem:
http://mail.python.org/pipermail/c++-sig/2008-April/013448.html )

But I had a look on Valgrind and found it very promising :)

The next time in a similar situation I will definitely give it a try!

Thanks again,

Dietrich




More information about the Cplusplus-sig mailing list