Segmentation fault(LINUX) and no idea why!
Thomas Thiele
thiele at muc.das-werk.de
Wed Jul 5 08:29:32 EDT 2000
More information about the Python-list mailing list
Wed Jul 5 08:29:32 EDT 2000
- Previous message (by thread): Segmentation fault(LINUX) and no idea why!
- Next message (by thread): Segmentation fault(LINUX) and no idea why!
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hallo! In my program I create a new thread. In this new thread I fork and replace the child with an other program using excel. Normaly I have up to four threads with this procedure. So I have a number of threads and the same numbers of childs (the called program) The problem is sometimes (relativly seldom, so it's unreproducible ;-( ) I get a segmantation fault and the pytthon interpreter stops. But I if the segmentation fault happens, one of the childs is not running anymore. (I don't know is that the reason or a result) A little testprogram with the same construction shows that if a segmentaltion fault happens in one child, the parant keeps running. I get no traceback from the interpreter. My Question is, where can I look for the problem. Why does the interpreter (-> the whole program) die. What can be the reason?
- Previous message (by thread): Segmentation fault(LINUX) and no idea why!
- Next message (by thread): Segmentation fault(LINUX) and no idea why!
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list