Ubuntu
python2.5 package

Python 2.5 segmentation fault on ubuntu feisty amd64

Bug #133221 reported by David Watson
6
Affects Status Importance Assigned to Milestone
python2.5 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I am running ubuntu feisty amd64 on a dual opteron w/ 2 GB RAM. I have the latest updates installed for the various packages I'm using.

I have python 2.5, psycopg2, postgres 8.2, and webpy 0.2. When I execute my python script it handles the read request just fine, but the create causes python to segfault. I'll attach the files from /var/crash and the scripts just as soon as I can find where to upload them.

Revision history for this message
David Watson (davidthewatson) wrote :
Revision history for this message
David Watson (davidthewatson) wrote :
Revision history for this message
David Watson (davidthewatson) wrote :
Revision history for this message
David Watson (davidthewatson) wrote :

To reproduce:

Setup the postgres database according to the instructions here under databasing:

http://webpy.org/tutorial2.en

1) Run the script...

python dave.py

2) From a web browser, request http://localhost:8080/

3) type some text in the text box at the bottom of the form

4) click the create button

Expected result:

The browser should return to the form with the new row added.

Actual result:

The browser paints a blank page since python has seg faulted under the covers.

Revision history for this message
Andrea Corbellini (andrea.corbellini) wrote :

Thank you for your bug report and help making Ubuntu better.
Could you please try to obtain a backtrace following the instructions located at <https://wiki.ubuntu.com/Backtrace>?

Changed in python2.5:
status: New → Incomplete
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in python2.5:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.