I filed a bug report: https://code.djangoproject.com/ticket/32600
lauantai 27. maaliskuuta 2021 klo 18.38.15 UTC+2 Aapo Rista kirjoitti:
> I get "Segmentation fault: 11" when I'm trying to create any Multi*
> geometry on Macbook Air with M1 processor. I guess this related
I get "Segmentation fault: 11" when I'm trying to create any Multi*
geometry on Macbook Air with M1 processor. I guess this related to some
underlying library (GDAL, GEOS?), which is not working correctly on new CPU
architecture. On Intel Macbook Pro and Ubuntu 20.40 all Mu
es.txt and pip, and your code is in revision control,
> right?), then change the Apache configuration to use the new VE and restart.
>
> On Wed, Feb 17, 2016 at 7:00 AM, Mike Dewhirst > wrote:
>
> Try stopping Apache during the upgrade. I need to do that on Ubuntu.
>
> Good luck
stopping Apache during the upgrade. I need to do that on Ubuntu.
>
> Good luck
>
> *Connected by Motorola*
>
>
> Tanuka Dutta wrote:
>
>
>
>
> down votefavorite
> <http://stackoverflow.com/questions/35430173/trying-to-upgrade-django-on-centos-encounters-
gt;I am now trying to upgrade to Django 1.8.8. I activated the virtualenv and
>then executed the following command, but it encounters a segmentation fault
>each time.
>
>$pip2.7 install --upgrade django==1.8.8 Collecting django==1.8.8
>/home/syt_admin/.virtualenvs/vishwaas_env/lib/py
nd
>then executed the following command, but it encounters a segmentation fault
>each time.
>
>$pip2.7 install --upgrade django==1.8.8 Collecting django==1.8.8
>/home/syt_admin/.virtualenvs/vishwaas_env/lib/python2.7/sitepackages/pip/_vendor/requests/packages/urllib3/util/ssl_.py
down votefavorite
<http://stackoverflow.com/questions/35430173/trying-to-upgrade-django-on-centos-encounters-segmentation-fault#>
Hello,
I have a Linux CentOS 6.7 installation on a VM. A few months ago, I had -
compiled and installed Python 2.7.8 on it - installed virtualenv-13.1.2 in
8, 2015 at 5:45:40 PM UTC+3, Eugenio Trumpy wrote:
>>
>> Hello everybody,
>>
>> I'm very not so expert on django, I'm at the first experience.
>> I'm using django as backhand of geonode application.
>>
>> Geonode works quite fine, however durin
t the first experience.
> I'm using django as backhand of geonode application.
>
> Geonode works quite fine, however during a save map request from client
> side I got this apache2 segmentation fault:
>
> [Thu Oct 08 15:30:38.037330 2015] [core:error] [pid 10101] [client
> X.
Hello everybody,
I'm very not so expert on django, I'm at the first experience.
I'm using django as backhand of geonode application.
Geonode works quite fine, however during a save map request from client
side I got this apache2 segmentation fault:
[Thu Oct 08 15:30:38.037330 20
d pid 11979 exit signal Segmentation
> fault (11)
> [Tue Jan 13 23:46:12 2015] [notice] child pid 11993 exit signal Segmentation
> fault (11)
>
> how do i go about resolving this?
You need to ensure that your Python/C libraries are up to date with your system.
Regards,
Xavier Ordo
/usr/local/lib/python2.7/dist-packages is being added to sys.path
[Tue Jan 13 23:46:11 2015] [error] from pkg_resources import
resource_stream
[Tue Jan 13 23:46:12 2015] [notice] child pid 11979 exit signal
Segmentation fault (11)
[Tue Jan 13 23:46:12 2015] [notice] child pid 11993 exit signal
Subject: Re: Segmentation fault
Try to update both your python and your mysql<-> python bindings. The libraries
you are using are either incompatible or have a bug.
Good luck
Sexta-feira, 8 de Agosto de 2014 5:21:44 UTC+1, Tianwei Sheng escreveu:
Hi, all,
Recently I constantly met segmen
Try to update both your python and your mysql<-> python bindings. The
libraries you are using are either incompatible or have a bug.
Good luck
Sexta-feira, 8 de Agosto de 2014 5:21:44 UTC+1, Tianwei Sheng escreveu:
>
> Hi, all,
>
> Recently I constantly met segmentation f
Hi, all,
Recently I constantly met segmentation fault for my django server(started
by runserver). The following is the trace I got from gdb (if not with gdb,
I only can see segmentation fault). I knew this
may not be a django issues, or even python issue, but anyone met similar
issues or
13:18:45)
>>>
>>> [GCC 4.2.1 (Apple Inc. build 5666) (dot 3)] on darwin
>>>
>>> Type "help", "copyright", "credits" or "license" for more information.
>>>
>>> (InteractiveConsole)
>>>
>>> &g
formation.
>>
>> (InteractiveConsole)
>>
>> >>> from polls.models import Poll, Choice
>>
>> >>> Poll.objects.all()
>>
>> Segmentation fault: 11
>>
>>
>> This type of thing just started after upgrade. I assume th
quot;, "credits" or "license" for more information.
>
> (InteractiveConsole)
>
> >>> from polls.models import Poll, Choice
>
> >>> Poll.objects.all()
>
> Segmentation fault: 11
>
>
> This type of thing just started after u
On 10/24/13 2:34 PM, Don Fox wrote:
...
Segmentation fault: 11
This type of thing just started after upgrade. I assume there's a
connection.
I found a similar symptom with another application after doing piecemeal
updates in MacPorts packages, and my problems went away with a
gt;>> from polls.models import Poll, Choice
>>> Poll.objects.all()
Segmentation fault: 11
This type of thing just started after upgrade. I assume there's a
connection.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubsc
On 05/13/2013 03:03 PM, Fernando Rocha wrote:
I find weird pygame reference there, do you also have pygame
installed)?
I've just tested on a env without pygame and:
In [4]: In [6]: lgdal['GDALVersionInfo'](b'RELEASE_NAME')
zsh: segmentation fault (core dumped) pytho
> I find weird pygame reference there, do you also have pygame
> installed)?
>
I've just tested on a env without pygame and:
In [4]: In [6]: lgdal['GDALVersionInfo'](b'RELEASE_NAME')
zsh: segmentation fault (core dumped) python manage.py shell
--
You rec
6]: lgdal['GDALVersionInfo'](b'RELEASE_NAME')
Fatal Python error: (pygame parachute) Segmentation Fault
zsh: abort (core dumped) python manage.py shell
---
I find weird pygame reference there, do you also have pygame
installed)?
[]s
On May 13, 5:29 am, Alessandro Candini wrote:
>
DataSource
Going back between exceptions, I found that the segmentation fault is
caused by line 84 of
/usr/lib/python2.7/site-packages/django/contrib/gis/gdal/libgdal.py:
ver = gdal_version().decode()
This is inside the gdal_version_info() function.
Have you got any idea on how to solve this?
Thanks
Hi Florian,
I have been working on the problem the whole weekend and after trying
all the mog_wsgi debugging method I still do not have a solution. I do
know that the error does not lie in my django code or my apache
configuration as I did the exact setup on a ubuntu machine and it
works 100%. It
Increase debug level and make sure to read the debugging docs on
modwsgi.org; then you can hopefully provide more info, so we can actually
help.
Cheers,
Florian
P.S.: Btw telling us which versions you use exactly would help too
--
You received this message because you are subscribed to the Go
odules the mod_wsgi apache server
raises a 500 error.
I did the whole installation using apt-get and installed pygtk.
I would appreciate any help to try and debug this issue. The only
thing in my apache error.log is :
child pid 3642 exit signal Segmentation fault (11)
Thanks
--
You received th
odules the mod_wsgi apache server
raises a 500 error.
I did the whole installation using apt-get and installed pygtk.
I would appreciate any help to try and debug this issue. The only
thing in my apache error.log is :
child pid 3642 exit signal Segmentation fault (11)
Thanks
--
You received th
Hi
I'm having the same problem. I'm using /mod_php5-5.2.9.so
With that loaded my worker processes crash as soon as they are started
and I get the segmentation fault in the logs.
No mod_python.
Did you fix this?
Thanks
Justin
On Oct 3, 3:54 pm, Олег Корсак
wrote:
> Hello. I&#
2.16 (Unix) + mpm_worker on my ~amd64
>> Gentoo Linux box. It has mod_php enabled and all my existing php
>> projects work fine (with mysql too).
>>
>> When I'm enabling mod_wsgi in apache config and trying to run simple
>> empty django project - I'm gett
my existing php
> projects work fine (with mysql too).
>
> When I'm enabling mod_wsgi in apache config and trying to run simple
> empty django project - I'm getting 500 Internal Server Error and
> "Segmentation fault" in error_log.
>
> When disabling mod_php - it r
Internal Server Error and
"Segmentation fault" in error_log.
When disabling mod_php - it runs just ok.
Any ideas? I need them both :)
Thanks
signature.asc
Description: OpenPGP digital signature
I had a large table of zip & postal codes which always crashed after
about 20 minutes of geocoding them in the ipython shell, i did the
same thing several times on the same os, but on a 32-bit machine with
no issues. running under mod-python or mod-wsgi on the 64-bit box
also seems to randomly th
> "The same problem [segfault] could afflict any python package that
> uses Ctypes on 64-bit systems without explicitly marking argument and
> return types. "
>
> Looking back through the modwsgi thread and this one, everyone's on
> 64bit, except the CentOS guy who said it worked ok on 32bit but n
Hi,
On Dec 3, 5:21 pm, Andre P LeBlanc <[EMAIL PROTECTED]> wrote:
> Confirmed also. only happens on my 64-bit machine, and is not related
> to apache at all as I can reproduce it faithfully in ipython.
>
I tried pretty hard to replicate it in the console and couldn't - none
of our unit tests cra
Confirmed also. only happens on my 64-bit machine, and is not related
to apache at all as I can reproduce it faithfully in ipython.
On Dec 2, 8:32 pm, GRoby <[EMAIL PROTECTED]> wrote:
> I can confirm that all of my seg faults were all on my 64 bit machine
> but could not be duplicated when I trie
I can confirm that all of my seg faults were all on my 64 bit machine
but could not be duplicated when I tried to on my 32 bit test virtual
machines.
On Dec 2, 7:40 pm, rcoup <[EMAIL PROTECTED]> wrote:
> Posting to geos-devel, I got this reply from Paul
> Ramsey:http://lists.osgeo.org/pipermail
On Dec 3, 1:40 pm, rcoup <[EMAIL PROTECTED]> wrote:
> Leading me to:http://sgillies.net/blog/829/shapely-1-0-8/
>
> "The same problem [segfault] could afflict any python package that
> uses Ctypes on 64-bit systems without explicitly marking argument and
> return types. "
The relevant changeset i
Posting to geos-devel, I got this reply from Paul Ramsey:
http://lists.osgeo.org/pipermail/geos-devel/2008-December/003800.html
Leading me to: http://sgillies.net/blog/829/shapely-1-0-8/
"The same problem [segfault] could afflict any python package that
uses Ctypes on 64-bit systems without expl
On Nov 26, 6:07 am, Justin Bronn <[EMAIL PROTECTED]> wrote:
> I created an Ubuntu 8.10 VM to try and test out this problem.
> However, the only way that I could reproduce your exact problem
> (segfault upon HTTP request) is when using the mpm-worker (threaded)
> Apache. When using the prefork,
FWIW --
I got this working in CentOS5.2 by removing the default (yum installed)
version of apache, and compiling the latest version, 2.2.10.
While I was at it, I compiled the latest version of mod_python.
That was all it took, and now, no more segmentation violations.
Thanks,
Liam
Justin Bronn
> I reran my tests with the latest version of Apache on my 8.10 test
> machine. I am no longer getting the Segfaults with either worker or
> prefork. I am now getting an Invalid SRS type "wkt" error (that I
> assume you are now running into).
Yup that's the error I got: http://code.djangoprojec
Justin,
I reran my tests with the latest version of Apache on my 8.10 test
machine. I am no longer getting the Segfaults with either worker or
prefork. I am now getting an Invalid SRS type "wkt" error (that I
assume you are now running into).
I have tried several things (including downgrading
> Based on comments in a separate thread, GeoDango may have issues with
> multithreaded configuration. Which Apache MPM was being used for each
> Apache version, prefork or worker? The worker MPM uses threads and so
> that could be the culprit.
Yes -- the libraries GeoDjango uses, GEOS and GDAL,
get a plain white screen if any
>> code is executed that works with spatially enabled models. Otherwise
>> everything seems to be working (including an OpenLayers MapServer
>> view, so I know the DB is loaded correctly).
>>
>> In the error.log file, I get a single error per
> I highly reccomend you to switch to psycopg2 2.0.8
> After I did a switch to this version, I haven't seen any segmentation
> faults since 30 september 2008 (earlier I had them every few days).
Ys! It works! After I'd updated psycopg to version 2.0.8 the
problem just disappeared! It seems to
OK I'll give it a go when I get some time to try mod_wsgi. Thanks for
all the help regarding this matter.
On Nov 17, 10:30 am, Graham Dumpleton <[EMAIL PROTECTED]>
wrote:
> Can you try building mod_wsgi instead and see if it picks up the
> correct library?
>
> If it doesn't work, post the output
> Sometimes pages load well but sometimes I get "Internal Server Error"
> at the same URL. In this case I have to reload page once or twice to
> load it properly. I'm using FastCGI and after fault I can see the
> following message in the apache logs:
> "[error] [client 127.0.0.1] FastCGI: incomple
Both of them are using the mpm-worker package. I tested the 2.2.9
version with mpm-prefork and mpm-event, they all gave the same
Segmentation Fault errors (rebooting the server in between installing
each).
Greg
On Nov 18, 6:53 pm, Graham Dumpleton <[EMAIL PROTECTED]>
wrote:
>
th spatially enabled models. Otherwise
> > everything seems to be working (including an OpenLayers MapServer
> > view, so I know the DB is loaded correctly).
>
> > In the error.log file, I get a single error per attempted page view
> > like:
> > [Tue Nov 18 16:13:43
an OpenLayers MapServer
> view, so I know the DB is loaded correctly).
>
> In the error.log file, I get a single error per attempted page view
> like:
> [Tue Nov 18 16:13:43 2008] [notice] child pid 21074 exit signal
> Segmentation fault (11)
> [Tue Nov 18 16:16:59 2008] [notice
I know the DB is loaded correctly).
In the error.log file, I get a single error per attempted page view
like:
[Tue Nov 18 16:13:43 2008] [notice] child pid 21074 exit signal
Segmentation fault (11)
[Tue Nov 18 16:16:59 2008] [notice] child pid 21071 exit signal
Segmentation fault (11)
[Tue Nov 18
ed that one of the fastcgi processes died and another copy
appeared (by PIDs).
Before, I was trying to get it work with mod_python, but no success...
I got the same "Internal Server Error" and "Segmentation Fault
(11)" (or "Bus Error (10)" sometimes) in apache logs. One o
Can you try building mod_wsgi instead and see if it picks up the
correct library?
If it doesn't work, post the output from running 'configure' script
and running 'make' for mod_wsgi.
I trust mod_wsgi build process more than I do mod_python.
Graham
On Nov 17, 9:04 pm, huw_at1 <[EMAIL PROTECTED]
ls -ltr /usr/local/lib/python2.5/config/libpython2.5.so
lrwxrwxrwx 1 root root 21 Nov 12 10:48 /usr/local/lib/python2.5/config/
libpython2.5.so -> ../../libpython2.5.so
ls -ltr /usr/local/lib
-r-xr-xr-x 1 root root 4806649 Nov 11 11:22 libpython2.5.a
-r-xr-xr-x 1 root root 4806649 Nov 12 12
Did you do a 'ls -L' on the symlink to validate it pointed at
something?
The relative location of where the .so will be is more a hint as for
different systems it may not be in same relative location.
Graham
On Nov 13, 10:44 pm, huw_at1 <[EMAIL PROTECTED]> wrote:
> My apologies. I forgot to men
My apologies. I forgot to mention that I already tried what was
suggested in the article you pointed me at. I created a symlink in /
usr/local/lib/python2.5/config as directed however recompiling
mod_python still links to the library statically. Unless I missed a
step in the article I am starting
Because you have created the symlink for the .so file so it appears
next to the static library. It is arguably a a failing of standard
Python installer that it doesn't do this. What to do is explained in
document I previously pointed you at:
http://code.google.com/p/modwsgi/wiki/InstallationIss
ls -ltr /usr/local/lib
-r-xr-xr-x 1 root root 4806649 Nov 11 11:22 libpython2.5.a
-r-xr-xr-x 1 root root 4806649 Nov 12 12:49 libpython2.5.so.1.0
lrwxrwxrwx 1 root root19 Nov 12 12:49 libpython2.5.so ->
libpython2.5.so.1.0
echo $LD_LIBRARY_PATH
/usr/local/lib
ldd /usr/lo
On Nov 12, 11:44 pm, huw_at1 <[EMAIL PROTECTED]> wrote:
> echo '/usr/local/lib' >> /etc/ld.so.conf
>
> more /etc/ld.so.conf
>
> include ld.so.conf.d/*.conf
> /usr/local/lib
>
> ldd /usr/local/bin/python
>
> libpython2.5.so.1.0 => not found
> libpthread.so.0 => /lib64/libpthread.s
echo '/usr/local/lib' >> /etc/ld.so.conf
more /etc/ld.so.conf
include ld.so.conf.d/*.conf
/usr/local/lib
ldd /usr/local/bin/python
libpython2.5.so.1.0 => not found
libpthread.so.0 => /lib64/libpthread.so.0 (0x0039a4a0)
libdl.so.2 => /lib64/libdl.so.2 (0x0039
On Wed, Nov 12, 2008 at 03:22:02AM -0800, huw_at1 wrote:
>
> An update on this.
>
> 'which python' returns:
>
> libpython2.5.so.1.0 => not found
> libpthread.so.0 => /lib64/libpthread.so.0 (0x0039a4a0)
> libdl.so.2 => /lib64/libdl.so.2 (0x0039a460)
>
An update on this.
'which python' returns:
libpython2.5.so.1.0 => not found
libpthread.so.0 => /lib64/libpthread.so.0 (0x0039a4a0)
libdl.so.2 => /lib64/libdl.so.2 (0x0039a460)
libutil.so.1 => /lib64/libutil.so.1 (0x0039b340)
libm.so
I'm having difficulty getting the mod_python.so to link dynamically.
I'm trying to compile the python interpreter with the "--enable-
shared" and compiling mod_python with the "--with-python" flags.
However the "ldd" always shows the mod_python.so as not dynamically
linking to the python libraries
On Nov 10, 8:53 pm, huw_at1 <[EMAIL PROTECTED]> wrote:
> Hi Graham and thanks for the response again.
>
> I seem to remember when I originally built this 64-bit mod_python
> module I had a lot of difficulty. I was getting error messages which I
> solved by following the solution in this article:
Some more info. Apache also segfaults when I succesfully sign in to
the admin site.
On Nov 10, 9:53 am, huw_at1 <[EMAIL PROTECTED]> wrote:
> Hi Graham and thanks for the response again.
>
> I seem to remember when I originally built this 64-bit mod_python
> module I had a lot of difficulty. I was
Hi Graham and thanks for the response again.
I seem to remember when I originally built this 64-bit mod_python
module I had a lot of difficulty. I was getting error messages which I
solved by following the solution in this article:
http://agiletesting.blogspot.com/2007_10_01_archive.html
Althou
On Nov 7, 10:29 pm, huw_at1 <[EMAIL PROTECTED]> wrote:
> Graham thanks,
>
> First of all here is my httpd.conf file modules:
>
> # Example:
> # LoadModule foo_module modules/mod_foo.so
> #
>
> LoadModule python_module modules/mod_python.so
> #LoadModule dav_svn_module modules/mod_dav_svn.so
Graham thanks,
First of all here is my httpd.conf file modules:
# Example:
# LoadModule foo_module modules/mod_foo.so
#
LoadModule python_module modules/mod_python.so
#LoadModule dav_svn_module modules/mod_dav_svn.so
#LoadModule authz_svn_module modules/mod_authz_svn.so
#
So as you ca
On Nov 7, 2:38 am, huw_at1 <[EMAIL PROTECTED]> wrote:
> Hi all. I am having some real problems with this. I have an LDAP
> authentication backend that I have hooked up to my app. Standalone it
> appears to run fine. However when running it through my apache server
> I am seeing alot of segmentat
I tried running a strace on apache for this but I am still no wiser?
Anyone?
On Nov 6, 3:38 pm, huw_at1 <[EMAIL PROTECTED]> wrote:
> Hi all. I am having some real problems with this. I have an LDAP
> authentication backend that I have hooked up to my app. Standalone it
> appears to run fine. Howe
Hi all. I am having some real problems with this. I have an LDAP
authentication backend that I have hooked up to my app. Standalone it
appears to run fine. However when running it through my apache server
I am seeing alot of segmentation faults in my error log coupled with
the redirection page not
about
> fine for that database). I'm trying to convert to postgresql,
> everything is configured correct and when i execute 'python manage.py
> syncdb --noinput' I just nicely receive Segmentation fault.
>
> Since I have 3 django installations (don't ask, we'
ut' I just nicely receive Segmentation fault.
Since I have 3 django installations (don't ask, we're converting other
apps right now) I thought it could be manage.py using an outdated
django distribution, so I ran 'python manage.py --version', which
gives me nicely '1.
What version of django are you using?
Will other commands (like validate or runserver) work?
Is this an existing known-to-work django app, or are you running
something new?
Thanks!
Jeff Anderson
Chris Hoeppner wrote:
> Hi there,
>
> I'm getting a segmentation fault on syncdb. No
Hi there,
I'm getting a segmentation fault on syncdb. No further output. On a
pretty much vanilla ubuntu feisty box on grokthis.
Output is as follows:
# ./manage.py syncdb
Segmentation fault
#
I wonder if this is somewhat a known issue or am I the one missing
something? Never got this b
On 1/23/07, Rchard Peng <[EMAIL PROTECTED]> wrote:
> Nikolaus Schlemm wrote:
> > > Aha! Not sure why I didn't think of that, but a back and forth
> > > switching php modules on and off eventually led me to mhash.so -
> > > switching off that module solved all my woes.
> > ouch mhash again ... a co
upgrade your MySQL-python to the latest will resolve the problem
Nikolaus Schlemm wrote:
> > Aha! Not sure why I didn't think of that, but a back and forth
> > switching php modules on and off eventually led me to mhash.so -
> > switching off that module solved all my woes.
> ouch mhash again ...
> Aha! Not sure why I didn't think of that, but a back and forth
> switching php modules on and off eventually led me to mhash.so -
> switching off that module solved all my woes.
ouch mhash again ... a couple of months ago that interfered with md5 for some
reason resulting in wrong digests, but
Hi Nikl,
> - have you tried to increase apache's loglevel?
Yes, but the errors were no more verbose.
> - do you have any php-extensions installed? if so, you might want
> to check out
> if php is really the factor by loading it without any extensions.
> if that
> works, try adding them bac
hi James,
> I'm running Ubuntu Edgy Eft, with the following versions (updated to
> the most recent available from apt-get)
> Apache/2.0.55 (Ubuntu) mod_python/3.2.8 Python/2.4.4c1 PHP/5.1.6
> mod_ssl/2.0.55 OpenSSL/0.9.8b
> and Django 0.95.
I'm running pretty much the same combo, but with
(http://www.djangoproject.com/
documentation/modpython/) I have installed mod_python but when
attempting to view a project I am getting Segmentation faults.
[Thu Jan 11 10:44:37 2007] [notice] child pid 10819 exit signal
Segmentation fault (11)
I followed the tests here (http://www.dscpl.com.au
here.
>
> Thanks very much for this fine collection of information and links.
> I've updated the documentation:
>
> http://www.djangoproject.com/documentation/modpython/#if-you-get-a-
> segmentation-fault
>
> Adrian
>
> --
> Adrian Holovaty
> holovaty.com | d
ks.
I've updated the documentation:
http://www.djangoproject.com/documentation/modpython/#if-you-get-a-segmentation-fault
Adrian
--
Adrian Holovaty
holovaty.com | djangoproject.com | chicagocrime.org
--~--~-~--~~~---~--~~
You received this message because you are
Graham King wrote:
>
>
> paolo wrote:
>
>>Hi, I had problems running Django with mod_python, so I had the
>>possibility to investigate and obtain some detailed info, which I'd
>>like to share here.
>>
>>I'd like to suggest "Expat Causing Apache Crash", which explains
>>problems caused due to
paolo wrote:
> Hi, I had problems running Django with mod_python, so I had the
> possibility to investigate and obtain some detailed info, which I'd
> like to share here.
>
> I'd like to suggest "Expat Causing Apache Crash", which explains
> problems caused due to mismatches in the version of t
Yes, that is the case.
Jacob Kaplan-Moss wrote:
> On Feb 15, 2006, at 4:19 PM, Graham King wrote:
>
>> I have been getting a segmentation fault when using
>>django.utils.feedgenerator to generate an RSS feed of my site. This
>>works fine with 'django-admin r
Again, it's useful to locate which is the problematic module (if it's
true that an imported module causes the crash) that make the
segmentation fault happen. For this I'd like to cite textually the
answer I had on mod_python mailing list (here is the whole thread, in
case anyone wou
On 2/15/06, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
> On Feb 15, 2006, at 4:19 PM, Graham King wrote:
> > I have been getting a segmentation fault when using
> > django.utils.feedgenerator to generate an RSS feed of my site. This
> > works fine with 'djang
On Feb 15, 2006, at 4:19 PM, Graham King wrote:
> I have been getting a segmentation fault when using
> django.utils.feedgenerator to generate an RSS feed of my site. This
> works fine with 'django-admin runserver', but when run under
> mod_python,
99% of the time
Dear django-users,
I have been getting a segmentation fault when using
django.utils.feedgenerator to generate an RSS feed of my site. This
works fine with 'django-admin runserver', but when run under mod_python,
I get (in Apache's error log):
[Wed Feb 15 22:02:4
91 matches
Mail list logo
