python2 crash traceback was not caught, yet python3 one was

Bug #1287659 reported by Dimitri John Ledkov
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Whilst investigating dial-number crash induced by dialer-app AP tests, we noticed that whilst both python2+pygtk and python3+gi based scripts crash, only the python3+gi edition generated a .crash file, the python2 edition does not.

This falsely suggested there was a regression, when python2 crash was simply not caught...

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

ev says to move this to apport.

affects: whoopsie (Ubuntu) → apport (Ubuntu)
Oliver Grawert (ogra)
Changed in apport (Ubuntu):
status: New → Confirmed
Revision history for this message
Martin Pitt (pitti) wrote :

I'm afraid it's not possible for the python3 module to run the python2 except hook. If we want to catch python 2 crashes on the phone, we need to install python-apport.

Changed in apport (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Dimitri John Ledkov (xnox) wrote : Re: [Bug 1287659] Re: python2 crash traceback was not caught, yet python3 one was

On 12 March 2014 05:18, Martin Pitt <email address hidden> wrote:
> I'm afraid it's not possible for the python3 module to run the python2
> except hook. If we want to catch python 2 crashes on the phone, we need
> to install python-apport.
>

Ok. We instead moving to python3-only, it's just we need to be aware
that "python3 crash reports" may be not regressions, but rather
"previously not reported".

--
Regards,

Dimitri.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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