use:
num_arr1 = numpy.array(tgt_arr1, dtype=int)
num_arr2 = numpy.array(tgt_arr2, dtype=int)
On Mon, Sep 16, 2019 at 5:36 PM Pradeep Patra
wrote:
> Yes it is crashing in the hackerrank site and the testcases fails with
> segmentation fault. I tried to install numpy with 3.7.3 and it
Thomas Jollans wrote:
> Please reply on-list. (both of you)
>
>
> Forwarded Message ----
> Subject: Re: numpy results in segmentation fault
> Date: Mon, 16 Sep 2019 17:04:57 +0530
> From: Test Bot
> To: Pradeep Patra
> CC: Thomas Jollans
>
> Firstly,
Please reply on-list. (both of you)
Forwarded Message
Subject:Re: numpy results in segmentation fault
Date: Mon, 16 Sep 2019 17:04:57 +0530
From: Test Bot
To: Pradeep Patra
CC: Thomas Jollans
Firstly, in response to this
"
I tried to install
Yes it is crashing in the hackerrank site and the testcases fails with
segmentation fault. I tried to install numpy with 3.7.3 and it is for some
reason not working and after import when I run import numpy at python
console and press enter I get >>? i,e its not working properly.
Can you
On 12/09/2019 15.53, Pradeep Patra wrote:
> Hi ,
>
> I was trying to solve the hackerrank and was using python 3.7.x.
> https://www.hackerrank.com/challenges/np-concatenate/problem
>
> While running the code sometimes I get success result and sometimes it
> fails with &q
Hi ,
I was trying to solve the hackerrank and was using python 3.7.x.
https://www.hackerrank.com/challenges/np-concatenate/problem
While running the code sometimes I get success result and sometimes it
fails with "Segmentation Fault" at Hacker rank UI. I dont have any clue why
t
Hey there,
I'm not sure this is the correct list considering the level of internal
Python knowledge it likely requires. If I should take this to another
list, please let me know.
I have written an application that links against libpython and starts
multiple interpreters within one thread. Beyond
varun...@gmail.com writes:
> Hello Everyone,
>
> I am trying to solve a mixed-integer problem using Cplex Python API
> and I get this error Segmentation fault (core dumped). i am not able
> to figure out the reason for this.
> Traceback
>
> srva@hades:~$ python RW10.py
On 06/01/2014 12:28 PM, varun...@gmail.com wrote:
Hello Everyone,
I am trying to solve a mixed-integer problem using Cplex Python API and I get
this error Segmentation fault (core dumped). i am not able to figure out the
reason for this.
Traceback
srva@hades:~$ python RW10.py --output test
Hello Everyone,
I am trying to solve a mixed-integer problem using Cplex Python API and I get
this error Segmentation fault (core dumped). i am not able to figure out the
reason for this.
Traceback
srva@hades:~$ python RW10.py --output test --logPath log --xml topology.xml
Start Time: 2014-6
I try gdb the executable file in another machine
and get this:
Error -3 from inflate: incorrect header check
Error decompresing struct
if I do gdb in my machine (where I generate the executable file)
I get nothing, and the app work correctly.
I try to search about that, but i don't get it.
Coul
t ugly output.
> shape-engine='BasicEngineFc', font='DejaVu Sans 10.9990234375', text=''
>
>
>
> (python:10096): Pango-CRITICAL **: pango_layout_get_line_count: assertion
> `layout != NULL' failed
>
>
>
> (python:10096): Gdk-CRI
On 4/23/2014 3:46 PM, Mark H Harris wrote:
On 4/23/14 1:08 PM, Reginaldo wrote:
I have a GUI app that is written using wx. When I run it on CentOS
6.5, the following error messages are displayed and the app closes:
Only fails on CentOS ?
I use an idle thread in my application.
Is
On 4/23/14 1:08 PM, Reginaldo wrote:
I have a GUI app that is written using wx. When I run it on CentOS 6.5, the
following error messages are displayed and the app closes:
Only fails on CentOS ?
I use an idle thread in my application.
Is your CentOS launching idle with -n switch ?
7;, text=''
(python:10096): Pango-CRITICAL **: pango_layout_get_line_count: assertion
`layout != NULL' failed
(python:10096): Gdk-CRITICAL **: IA__gdk_draw_layout: assertion
`PANGO_IS_LAYOUT (layout)' failed
Segmentation fault
I checked if this was a font issue, but the font is
Hi.
On 4.4.2014. 11:17, Chris Angelico wrote:
But from here you need someone more familiar with cxfreeze. All I
can advise is to compare installed packages on each; maybe you
have multiple versions of some library or something.
From what little I know of it, it freezes as little as possibl
executable
under gdb; instead of getting a simple "Segmentation fault" message,
you get some chance at a bit more info. But from here you need someone
more familiar with cxfreeze. All I can advise is to compare installed
packages on each; maybe you have multiple versions of some li
; > Hello,
>
> > I generated an executable python file using cxfreeze.
>
> > I run that file, it runs fine.
>
> > But when I run it on another PC, it don't run. I try to it via terminal,
> > and it says "Segmentation fault(core dump)". I
On Fri, Apr 4, 2014 at 7:36 PM, wrote:
> Hello,
> I generated an executable python file using cxfreeze.
> I run that file, it runs fine.
> But when I run it on another PC, it don't run. I try to it via terminal, and
> it says "Segmentation fault(core dump)". I
Hello,
I generated an executable python file using cxfreeze.
I run that file, it runs fine.
But when I run it on another PC, it don't run. I try to it via terminal, and it
says "Segmentation fault(core dump)". I try again run it with sudo, it says
nothing and nothing happend.
C
John Ladasky wrote:
> I am trying to help a student of mine install Python 3 on his MacBook Pro.
> Follow-up questions: if I need a more current GCC for my student's Mac,
> how do I obtain it? And are there any backwards-compatibility issues I
> might need to worry about if I do upgrade? From m
On 06/11/2013 20:47, John Ladasky wrote:
Thanks, Mark.
Reading through the information in your link, I appear to have encountered an
actual bug specific to Python 3.3.2 and OS X 10.9. And it appears that the
3.3.3 version of Python that fixes this bug is still in beta. And that I can
have m
Thanks, Mark.
Reading through the information in your link, I appear to have encountered an
actual bug specific to Python 3.3.2 and OS X 10.9. And it appears that the
3.3.3 version of Python that fixes this bug is still in beta. And that I can
have my student download the working version from
, giving
the error "Segmentation fault: 11".
I have installed Python 3 on Linux and on Windows before, but I have no prior
experience with Macs. I know that OSX is Unix-like, but I'm sure that there
are significant differences between the Linux that I normally use and OSX.
My stu
I am trying to help a student of mine install Python 3 on his MacBook Pro. The
installation succeeds. However, upon opening the Python interpreter, he can
only execute one Python command successfully. On the second command, the
interpreter crashes, giving the error "Segmentation faul
Am 10.10.2011 14:18, schrieb X1:
has this bug been resolved?
if yes, which version on files to install?
That seems to be part of PyOpenGL, so I'd check their bugtracking system.
Uli
--
http://mail.python.org/mailman/listinfo/python-list
On Aug 6, 6:35 am, Vipul Raheja wrote:
> Hi,
>
> I have wrapped a library from C++ to Python using SWIG. But when I
> import it in Python, I am able to work fine with it, but it gives a
> segmentation fault while exiting. Following is the log:
>
> vipul@vipul-laptop:~/ossim
On Sat, Aug 6, 2011 at 3:35 AM, Vipul Raheja wrote:
> Hi,
>
> I have wrapped a library from C++ to Python using SWIG. But when I
> import it in Python, I am able to work fine with it, but it gives a
> segmentation fault while exiting. Following is the log:
>
> vipul@vipul-l
Vipul Raheja wrote:
> I have wrapped a library from C++ to Python using SWIG. But when I
> import it in Python, I am able to work fine with it, but it gives a
> segmentation fault while exiting.
1. Use a debugger
Run python with "gdb python", import the module and exit. The de
On Sat, Aug 6, 2011 at 2:34 PM, Vipul Raheja wrote:
> Here's the link: www.geofemengineering.it/data/master_wrap.cxx
> Thanks and Regards,
> Vipul Raheja
Ugh. Unfortunately that file is somewhat lengthy... I hate to say
"tl;dr" to people, but... is there any way to simplify that down?
Perhaps th
t it in Python, I am able to work fine with it, but it gives a
> segmentation fault while exiting. Following is the log:
>
> vipul@vipul-laptop:~/ossim-svn/src/pyossim/swig$ python
> Python 2.6.6 (r266:84292, Sep 15 2010, 15:52:39)
> [GCC 4.4.5] on linux2
> Type "help",
Hi,
I did look out for the problem's solution but have been struggling with it
ever since. I also asked around on IRC too but haven't quite progressed
towards the solution. Here is the link to the swig-generated .cxx file which
we need to look into for the answers. Could you please have a look at
On Sat, Aug 6, 2011 at 12:16 PM, Vipul Raheja wrote:
> Hi Chris,
> Thanks for the reply.
> However, the error occurs even if I don't do anything, that is, even if I
> simply import the library and exit() after that.
> I created a file a.py whose contents were the following:
> import pyossim
> exit
aptop:~/ossim-svn/src/pyossim/swig$ python a.py
Segmentation fault
Following was the gdb log:
vipul@vipul-laptop:~/ossim-svn/src/pyossim/swig$ gdb `which python`
GNU gdb (GDB) 7.2-ubuntu
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http:/
On Sat, Aug 6, 2011 at 11:35 AM, Vipul Raheja wrote:
> Hi,
>
> I have wrapped a library from C++ to Python using SWIG. But when I
> import it in Python, I am able to work fine with it, but it gives a
> segmentation fault while exiting. Following is the log:
The most likely cause
Hi,
I have wrapped a library from C++ to Python using SWIG. But when I
import it in Python, I am able to work fine with it, but it gives a
segmentation fault while exiting. Following is the log:
vipul@vipul-laptop:~/ossim-svn/src/pyossim/swig$ python
Python 2.6.6 (r266:84292, Sep 15 2010, 15:52
hi all,
i can't get connected to bugs.python.org
so here my make test results.
make test aborted when running test_ftplib.
and running
# ./python Lib/test/test_ftplib.py
Segmentation fault
with this kernel message:
[ 2166.927138] python[12142]: seg
the code is not mine, and it takes
> > > over a day for me to get the point where the segmentation
> > > fault occurred. Plus, it seems that the point is not
> > > deterministic
>
> > > Still, I think I should at least try to figure out exactly
> > > a
On Mittwoch 17 November 2010, Wolfgang Rohdewald wrote:
> On Mittwoch 17 November 2010, justin wrote:
> > But the problem is that the code is not mine, and it takes
> > over a day for me to get the point where the segmentation
> > fault occurred. Plus, it seems
On Mittwoch 17 November 2010, justin wrote:
> But the problem is that the code is not mine, and it takes
> over a day for me to get the point where the segmentation
> fault occurred. Plus, it seems that the point is not
> deterministic
>
> Still, I think I should at least
es the program in C crashes while it's being
> >> used in Python.
> >> Even under the circumstances, I want to get the Python program going
> >> by handling the segmentation fault.
>
> >> I've already searched the Internet, but couldn't get t
ython program going
by handling the segmentation fault.
I've already searched the Internet, but couldn't get the right answer
to catch them.
Could any of you please let me know how to deal with this and catch
the segmentation fault in Python?
Thanks,
Justin.
Segmentation fault isn't
thon program going
> by handling the segmentation fault.
>
> I've already searched the Internet, but couldn't get the right answer
> to catch them.
> Could any of you please let me know how to deal with this and catch
> the segmentation fault in Python?
You can't "
going
> by handling the segmentation fault.
>
> I've already searched the Internet, but couldn't get the right answer
> to catch them.
> Could any of you please let me know how to deal with this and catch
> the segmentation fault in Python?
>
> Thanks,
> Justin.
Segm
Hi all,
I am calling a program written in C inside Python using ctypes,
and it seems that sometimes the program in C crashes while it's being
used in Python.
Even under the circumstances, I want to get the Python program going
by handling the segmentation fault.
I've already se
On 8 Jul., 19:32, Christian Heimes wrote:
> Which third party products with C extensions do you use? Have you
> updated your database adapter and NumPy yet?
I'm using sqlalchemy, scipy and numpy. I will try to update these and
see if that helps.
Dierk
--
http://mail.python.org/mailman/listinf
> my python project crashes in a non reproducible way. With gdb I got
> the backtraces given below.
> How can I possibly figure out the reason for the segfaults that occur
> under Linux and Windows, using Python 2.6 in both cases.
One of your third party C extension has a reference count bug. It l
"dierkerdm...@mail.com" writes:
> my python project crashes in a non reproducible way. With gdb I got
> the backtraces given below.
> How can I possibly figure out the reason for the segfaults that occur
> under Linux and Windows, using Python 2.6 in both cases.
It's a big C program and you have
Hi,
my python project crashes in a non reproducible way. With gdb I got
the backtraces given below.
How can I possibly figure out the reason for the segfaults that occur
under Linux and Windows, using Python 2.6 in both cases.
Thanks
Dierk
Program received signal SIGSEGV, Segmentation fault
On Thu, Oct 15, 2009 at 9:08 PM, ankita dutta wrote:
> hi,
> well, even i was also using matplotlib for some time, and it was working
> fine.
> but this time i use it for data which is quite large,( my input file has
> single column of float values ,
> and length ( no. of rows) of this column is 1
hi,
well, even i was also using matplotlib for some time, and it was working
fine.
but this time i use it for data which is quite large,( my input file has
single column of float values ,
and length ( no. of rows) of this column is 10,000,000. )
may be because of size it might have crashed.
any wa
On Thu, Oct 15, 2009 at 7:46 PM, ankita dutta wrote:
> thanx david,
>
> yes ,i am using matplotlib for plotting graph.
> i am using this lines in my programme:
>
> "import matplotlib.pyplot as plt"
>
> now, if the problem with matplotlib ( and i will send them mail) ,
The problem is how matplotli
i in range (0,len(lines1)):
> > f1=lines1[i].split()
> > c1.append(float(f1[0]))
> > exp.append(i)
> > c1.sort(reverse=1)
> >
> > lines=plt.plot(c1,exp,'ro')
> > plt.show()
> > .
> > .
> > .
> >
> > but every
ta
On Thu, Oct 15, 2009 at 3:35 PM, David Cournapeau wrote:
> On Thu, Oct 15, 2009 at 6:14 PM, ankita dutta
> wrote:
>
> > is dumped
> > segmentation fault
> >
> >
>
> It looks like you are using matplotlib, and matplotlib is the one
> likely to segfault
:
> f1=lines1[i].split()
> c1.append(float(f1[0]))
> exp.append(i)
> c1.sort(reverse=1)
>
> lines=plt.plot(c1,exp,'ro')
> plt.show()
> .
> .
> .
>
> but every time its showing the following error:
>
> is dumped
> segmentation
; f1=lines1[i].split()
> c1.append(float(f1[0]))
> exp.append(i)
> c1.sort(reverse=1)
>
> lines=plt.plot(c1,exp,'ro')
> plt.show()
> .
> .
> .
>
> but every time its showing the following error:
>
> is dumped
> segmentation fault
The p
On Thu, Oct 15, 2009 at 6:14 PM, ankita dutta wrote:
> is dumped
> segmentation fault
>
>
It looks like you are using matplotlib, and matplotlib is the one
likely to segfault. You could check that it is indeed the case by just
commenting the part which does the plot - but I w
)
*.
.
.
but every time its showing the following error:
* is dumped
segmentation fault*
can anyone kindly help me out
thank you.
ankita
--
http://mail.python.org/mailman/listinfo/python-list
On Apr 14, 9:00 pm, bieff...@gmail.com wrote:
> On Apr 15, 12:39 am, sanket wrote:
>
>
>
> > Hello All,
>
> > I am dealing with this weird bug.
> > I have a function in C and I have written python bindings for it using
> > ctypes.
>
> > I can call this function for couple of times and then suddenl
>
> Thanks Diez,
>
> I used the gdb but it just crashed and kicked my out of gdb prompt.
> how can I get a stack trace?
That's odd, has never happened for me before. Can you show us what you do
exactly, and what gdb & co say?
Diez
--
http://mail.python.org/mailman/listinfo/python-list
On Apr 15, 12:39 am, sanket wrote:
> Hello All,
>
> I am dealing with this weird bug.
> I have a function in C and I have written python bindings for it using
> ctypes.
>
> I can call this function for couple of times and then suddenly it
> gives me seg fault.
> But I can call same function from a
On Apr 14, 6:45 pm, Aaron Brady wrote:
> On Apr 14, 6:04 pm, sanket wrote:
>
>
>
> > On Apr 14, 4:00 pm, MRAB wrote:
>
> > > sanket wrote:
> > > > Hello All,
>
> > > > I am dealing with this weird bug.
> > > > I have a function in C and I have written python bindings for it using
> > > > ctypes.
Aaron Brady wrote:
On Apr 14, 6:04 pm, sanket wrote:
On Apr 14, 4:00 pm, MRAB wrote:
sanket wrote:
Hello All,
I am dealing with this weird bug.
I have a function in C and I have written python bindings for it using
ctypes.
I can call this function for couple of times and then suddenly it
On Apr 14, 6:04 pm, sanket wrote:
> On Apr 14, 4:00 pm, MRAB wrote:
>
>
>
> > sanket wrote:
> > > Hello All,
>
> > > I am dealing with this weird bug.
> > > I have a function in C and I have written python bindings for it using
> > > ctypes.
>
> > > I can call this function for couple of times an
sanket wrote:
On Apr 14, 4:00 pm, MRAB wrote:
sanket wrote:
Hello All,
I am dealing with this weird bug.
I have a function in C and I have written python bindings for it using
ctypes.
I can call this function for couple of times and then suddenly it
gives me seg fault.
But I can call same func
On Apr 14, 3:56 pm, "Diez B. Roggisch" wrote:
> sanket schrieb:
>
> > Hello All,
>
> > I am dealing with this weird bug.
> > I have a function in C and I have written python bindings for it using
> > ctypes.
>
> > I can call this function for couple of times and then suddenly it
> > gives me seg f
On Apr 14, 4:00 pm, MRAB wrote:
> sanket wrote:
> > Hello All,
>
> > I am dealing with this weird bug.
> > I have a function in C and I have written python bindings for it using
> > ctypes.
>
> > I can call this function for couple of times and then suddenly it
> > gives me seg fault.
> > But I ca
sanket wrote:
Hello All,
I am dealing with this weird bug.
I have a function in C and I have written python bindings for it using
ctypes.
I can call this function for couple of times and then suddenly it
gives me seg fault.
But I can call same function from a C code for any number of times.
I
sanket schrieb:
Hello All,
I am dealing with this weird bug.
I have a function in C and I have written python bindings for it using
ctypes.
I can call this function for couple of times and then suddenly it
gives me seg fault.
But I can call same function from a C code for any number of times.
Hello All,
I am dealing with this weird bug.
I have a function in C and I have written python bindings for it using
ctypes.
I can call this function for couple of times and then suddenly it
gives me seg fault.
But I can call same function from a C code for any number of times.
I cannot get what'
I have a multithreaded python app running on FreeBSD (both 7.0 and
6.3) that crashes with a segmentation fault coming from
PyObjectMalloc. This first happened using Python 2.5 built from Ports.
I then pulled down r261 from Subversion and built that so I would have
debugging symbols; it still
to it guarded by a
reader lock which i got from recipe :
The problem is during the re-loading of the library
occasionally the python script will abort with "Segmentation Fault".
This is like 1 out of 10 times it can happen and that
is good enough to kill the application.
Is
reader lock which i got from recipe :
http://code.activestate.com/recipes/413393/
The problem is during the re-loading of the library occasionally the
python script will abort with "Segmentation Fault". This is like 1 out
of 10 times it can happen and that
is good enough t
Hello All,
I Need some tips/help/ideas debugging segmentation fault ...
I'm trying to debug Python running embedded inside a Verilog
Simulator (as a SystemVerilog DPI application). (on SUSE LINUX
Enterprise Server 9 (i586))
The Embedded python loads two SWIG wrapped modules (written in
[EMAIL PROTECTED] wrote:
Hi - I am very new to python. I get this random core dump and am
looking for a good way to catch the error. I know the function my core
dump occurs. Is there any error catching/handling that I could use in
python?
When posting such questions, please supply Python vers
Doug Morse wrote:
> Well, I must be missing something re: why Stefan states that you are using
> Windows. I don't see that stated in your original post
It's stated in the mail headers of his post, though. That's the problem with
newbies - you never know where that stops being right.
Stefan
--
ht
On Fri, 18 Jul 2008 15:56:10 +0200, Stefan Behnel <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> > Hi - I am very new to python. I get this random core dump and am
> > looking for a good way to catch the error. I know the function my core
> > dump occurs. Is there any error catching/handl
anks for responding. I am actually running on linux. Does this
make a difference? Also the error shown is:
myFunction call failed. Segmentation Fault (core dumped)
--
http://mail.python.org/mailman/listinfo/python-list
[EMAIL PROTECTED] wrote:
> Hi - I am very new to python. I get this random core dump and am
> looking for a good way to catch the error. I know the function my core
> dump occurs. Is there any error catching/handling that I could use in
> python?
Since you are using Windows, this is somewhat non-t
I would suggest importing traceback.
import traceback
try :
mystuff
except :
print str(traceback.format_exc())
But in the case of a SegFault or core dump, it might not help you at all.
Can you post part of the function ?
On Fri, Jul 18, 2008 at 9:25 AM, <[EMAIL PROTECTED]> wrote:
> Hi -
Hi - I am very new to python. I get this random core dump and am
looking for a good way to catch the error. I know the function my core
dump occurs. Is there any error catching/handling that I could use in
python?
--
http://mail.python.org/mailman/listinfo/python-list
from duplicate limit 1')
> >>> d = cur.fetchone()
> >>> d
>
> (,
> )>>>
> map(str,d)
>
> ["\x02#qO\xb0\xcc\xfcx\xb9u\xa5\x83)\xc4'@", '\xa1\xf22\xf6y\xd0\xbc
> \xea6\xf0Y\xf1"\xc9(\n']>>> cur.ex
#x27;\xa1\xf22\xf6y\xd0\xbc
\xea6\xf0Y\xf1"\xc9(\n']
>>> cur.execute('UPDATE duplicate SET orig_sig=%(orig_sig)s WHERE duplicate.sig
>>> = %(duplicate_sig)s',
... dict(orig_sig=d[0], duplicate_sig=d[1]))
Segmentation fault
Am I (and SqlAlchemy) doing something silly or is this a bug in
psycopg2 ?
George
--
http://mail.python.org/mailman/listinfo/python-list
Hi,
I found the reason for the segmentation fault and hope that my solution
might be helpful for somebody else some day :)
On Tue, 2008-04-08 at 19:31 +0900, Dietrich Bollmann wrote:
Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0xb046ab90 (LWP 9
Hi,
Since some time I get the following segmentation fault in an
application which used to work fine until recently.
I made a backtrace but couldn't find the reason for the segmentaion
fault until now.
In the hope that somebody might have encountered a similar problem or
does understan
Hi,
Since some time I get the following segmentation fault in an
application which used to work fine until recently.
I made a backtrace but couldn't find the reason for the segmentaion
fault until now.
In the hope that somebody might have encountered a similar problem or
does understan
On 31 Mar, 20:52, kim <[EMAIL PROTECTED]> wrote:
> array_pointer_t = ndpointer(dtype=c_double)
This one is wrong. The dtype should be the datatype kept in the array,
which is 'float' (Python doubles) or 'numpy.float64'.
array_pointer_t = ndpointer(dtype=numpy.float64)
I'd take a good look at t
arge lists i got the same problem: Segmentation fault. for example
for the following two lines:
list1,list2 = numpy.array([0.1 for i in range(999)]),
numpy.array([0.7 for i in range(1041)])
print timewarp(list1,list2)
So it is maybe more of a c problem, but still, if i copy the big
arrays into my c c
On 30 Mar, 22:21, [EMAIL PROTECTED] wrote:
> Hello everybody,
>
> I'm building a python module to do some heavy computation in C (for
> dynamic time warp distance computation).
Why don't you just ctypes and NumPy arrays instead?
# double timewarp(double x[], int lenx, double y[], int leny);
imp
ry.
so, for example
list1,list2 = [0.1 for i in range(555)],[0.2 for i in range(1874)]
ctimewarp(list1,list2) # see python file below
works perfectly fine
and if the vector has one more element
list1,list2 = [0.1 for i in range(555)],[0.2 for i in range(1875)]
ctimewarp(list1,list2)
it dies with a
Program terminated with signal 11, Segmentation fault.
Environment: FreeBSD 6.2, Python 2.4.4, MySQLdb 1.2.2, SQLObject 0.9.1
I faced with an error in our multithreaded, network oriented application,
wich interacts actively with MySQL database.
Though I am not very experienced with FreeBSD and
Abandoned wrote:
> I run a my script and 3-4 minutes later give me an error
> "segmentation fault".
> What is the reason of this error ?
The reason is that the process tries to write to a memory address it
outside of its allocated segments.
Regards,
Björn
--
BOFH excuse #
Bruno Desthuilliers wrote:
> Jorge Godoy a écrit :
>> Without seeing any code, it is hard to say anything. But the answer to
>> the ultimate question is "42".
>
> Indeed. Err, what was the question, exactly ?-)
As soon as calculations are finished, you'll know. :-)
--
http://mail.python.org/ma
Jorge Godoy a écrit :
> Abandoned wrote:
>
>> Hi..
>> I run a my script and 3-4 minutes later give me an error "segmentation
>> fault".
>> What is the reason of this error ?
>>
>> I use in my script:
>> Threading
>> Psycopg2
>
Abandoned wrote:
> Hi..
> I run a my script and 3-4 minutes later give me an error "segmentation
> fault".
> What is the reason of this error ?
>
> I use in my script:
> Threading
> Psycopg2
> open & write to txt
> urlopen
>
> My platform is u
Hi..
I run a my script and 3-4 minutes later give me an error "segmentation
fault".
What is the reason of this error ?
I use in my script:
Threading
Psycopg2
open & write to txt
urlopen
My platform is ubuntu linux.
I'm sorry my bad english.
King regards..
--
http://mail
/local/lib/python2.5/test/test_compiler.py ...
Compiling /usr/local/lib/python2.5/test/test_complex.py ...
Compiling /usr/local/lib/python2.5/test/
test_complex_args.py ...
make: *** [libinstall] Segmentation fault
Any ideas on how to proceed? Do you need any additional
parseString
> > doc = parseString( "whatever" )
>
> > => blank screen, _no_any_exception_; Apache error_log:
> > [Fri Jan 26 10:18:48 2007] [notice] child pid 17596 exit signal
> > Segmentation fault (11)
>
> > Outsidemod_pythoncode works well. Any id
che error_log:
> [Fri Jan 26 10:18:48 2007] [notice] child pid 17596 exit signal
> Segmentation fault (11)
>
> Outside mod_python code works well. Any ideas? I would be grateful.
http://www.python.org/sf/1558223
http://www.python.org/sf/1295808
http://www.python.org/sf/1075984
Try
Python 2.4.4
mod_python 3.2.10 + Apache 2.0
def index( req, **params ):
from xml.dom.minidom import parseString
doc = parseString( "whatever" )
=> blank screen, _no_any_exception_; Apache error_log:
[Fri Jan 26 10:18:48 2007] [notice] child pid 17596 exit signal
Segmentat
1 - 100 of 170 matches
Mail list logo
