Re: how to debug when "Segmentation fault"

2005-10-05 Thread Maksim Kasimov
looks sad :( ok, until the decision not found, i've run my script (if someone have the same problem) using sh-script like this: #!/bin/sh while true do myscript.py echo "scrip was fault" | mail -s "run.sh" [EMAIL PROTECTED] done ... still works ;) Franz Steinhaeusler wrote: > Tamer, thanks

Re: how to debug when "Segmentation fault"

2005-10-05 Thread jepler
Interesting. I'd noticed that the metaclass one didn't crash my 2.2, but I didn't check the marshal one. This one core dumps in 'Python 2.2.2 (#1, Feb 24 2003, 19:13:11) ... linux2' but inexplicably prints 'keys' when I ran it on the 2.4.1 I used in my last post. >>> import marshal >>> f = lambd

Re: how to debug when "Segmentation fault"

2005-10-05 Thread Maksim Kasimov
[EMAIL PROTECTED] wrote: > I've rewritten your middle example to be clearer. > $ python2.4 > Python 2.4.1 (#1, May 16 2005, 15:15:14) > [GCC 4.0.0 20050512 (Red Hat 4.0.0-5)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > type("Y", (type,), {"mro": lambda

Re: how to debug when "Segmentation fault"

2005-10-05 Thread Franz Steinhaeusler
On Wed, 05 Oct 2005 14:53:45 +0200, Tamer Fahmy <[EMAIL PROTECTED]> wrote: >On Tue, 04 Oct 2005 19:13:10 +0300, Maksim Kasimov wrote: >> my programm sometime gives "Segmentation fault" message (no matter how >> long the programm had run (1 day or 2 weeks). And there is nothing in >> log-files that

Re: how to debug when "Segmentation fault"

2005-10-05 Thread Tamer Fahmy
On Tue, 04 Oct 2005 19:13:10 +0300, Maksim Kasimov wrote: > my programm sometime gives "Segmentation fault" message (no matter how > long the programm had run (1 day or 2 weeks). And there is nothing in > log-files that can points the problem. My question is how it possible to > find out where is t

Re: how to debug when "Segmentation fault"

2005-10-05 Thread Pierre Barbier de Reuille
Maksim Kasimov a écrit : > > yes, to generete core dump is the best way, > > but the command "$ ulimit -c 50" don't make python to generete core > dump in the time of crush. > > I would like to know how to run python script so if it crushes than core > dump will be genereted. > > Thanks >

Re: how to debug when "Segmentation fault"

2005-10-05 Thread Maksim Kasimov
yes, to generete core dump is the best way, but the command "$ ulimit -c 50" don't make python to generete core dump in the time of crush. I would like to know how to run python script so if it crushes than core dump will be genereted. Thanks Pierre Barbier de Reuille wrote: > Maksim Ka

Re: how to debug when "Segmentation fault"

2005-10-04 Thread jepler
I've rewritten your middle example to be clearer. $ python2.4 Python 2.4.1 (#1, May 16 2005, 15:15:14) [GCC 4.0.0 20050512 (Red Hat 4.0.0-5)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> type("Y", (type,), {"mro": lambda x: [float]})("X", (), {}) and here's

Re: how to debug when "Segmentation fault"

2005-10-04 Thread Michael Ekstrand
On Oct 4, 2005, at 2:08 PM, Jp Calderone wrote: > On Tue, 4 Oct 2005 11:22:24 -0500, Michael Ekstrand > <[EMAIL PROTECTED]> wrote: >> I've never seen "stock" Python (stable release w/ only included >> modules) >> segfault, but did see a segfault with an extension module I was using >> the other w

Re: how to debug when "Segmentation fault"

2005-10-04 Thread Jp Calderone
On Tue, 4 Oct 2005 11:22:24 -0500, Michael Ekstrand <[EMAIL PROTECTED]> wrote: >On Tuesday 04 October 2005 11:13, Maksim Kasimov wrote: >> my programm sometime gives "Segmentation fault" message (no matter >> how long the programm had run (1 day or 2 weeks). And there is >> nothing in log-files tha

[OT] Re: how to debug when "Segmentation fault"

2005-10-04 Thread Inyeol Lee
On Tue, Oct 04, 2005 at 11:22:24AM -0500, Michael Ekstrand wrote: [...] > I've never seen "stock" Python (stable release w/ only included modules) > segfault, but did see a segfault with an extension module I was using > the other week (lxml IIRC, but I'm not sure). > > - Michael So far, this i

Re: how to debug when "Segmentation fault"

2005-10-04 Thread Pierre Barbier de Reuille
Maksim Kasimov a écrit : > > Hello, > > my programm sometime gives "Segmentation fault" message (no matter how > long the programm had run (1 day or 2 weeks). And there is nothing in > log-files that can points the problem. > My question is how it possible to find out where is the problem in the

Re: how to debug when "Segmentation fault"

2005-10-04 Thread Maksim Kasimov
there are a lot of packeges under suspicion: cPickle, select, threading, logging, socket, struct Michael Ekstrand wrote: > On Tuesday 04 October 2005 11:13, Maksim Kasimov wrote: > >>my programm sometime gives "Segmentation fault" message (no matter >>how long the programm had run (1 day or 2

Re: how to debug when "Segmentation fault"

2005-10-04 Thread Michael Ekstrand
On Tuesday 04 October 2005 11:13, Maksim Kasimov wrote: > my programm sometime gives "Segmentation fault" message (no matter > how long the programm had run (1 day or 2 weeks). And there is > nothing in log-files that can points the problem. My question is how > it possible to find out where is the

how to debug when "Segmentation fault"

2005-10-04 Thread Maksim Kasimov
Hello, my programm sometime gives "Segmentation fault" message (no matter how long the programm had run (1 day or 2 weeks). And there is nothing in log-files that can points the problem. My question is how it possible to find out where is the problem in the code? Thanks for any help. Python 2