On Sat, 2007-05-26 at 02:20 -0700, Grant D. Watson wrote:
> Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
> > > In an unusually (for Ubuntu) boneheaded move, it
> > looks
> > > like Ubuntu doesn't leave core files for packaged
> > > programs, even after a "ulimit -c unlimited". Any
> > > other way to pull this off?
> >
> > I wouldn't have thought it was possible to
> > permanently disable that, so
> > my first thought would be you haven't changed the
> > limits for the right
> > process.
>
> Entirely possible, but I ran the "ulimit -c unlimited"
> in the same bash session that I subsequently ran the
> sync in.
>
> > Is Python crashing? Or the PostgreSQL
> > server?
>
> Python:
> ~$ python project/manage.py syncdb
> Segmentation fault (core dumped)
Oh, right. :-(
I think you're a little bit doomed here, if Ubuntu ships stripped
binaries. On a Fedora system I would install the *-debuginfo at this
point. Then you could try
gdb python
...
(gdb) run manage.py syncdb
and at least you will be in gdb when it crashes and can type "bt" to see
what's going on. Though, as I said, with stripped binaries this is going
to tell you nuffink.
I'm really not sure what else to suggest here.
One last idea: since you're using Python 2.5, you could try using the
sqlite3 backend (it's shipped standard with 2.5) and see if that gets
you through syncdb. No changes other than one line settings.py will be
needed. That might tell us what we already suspect (that psycopg2 is
involved somehow).
Cheers,
Malcolm
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
