> Obviously the right thing to do here is for the application to return
unique exceptions.
That's true, but wouldn't have helped here, since it is not an exception
that you throw explicitly, but just a bug in the code (not checking
whether we have a valid (not None) token).
The stack trace seems quite fine, and it crashes because of the very
same reason (accessing token before initializing). Now, of course there
can be multiple reasons why token == None, when fixing this all cases
should be taken into account.
If that is a very common crash situation and a "should not happen",
please check if token is None, and throw an assertion with a more
particular error message.
** Changed in: apport (Ubuntu)
Status: Confirmed => Won't Fix
--
Retracer incorrectly marked bugs as duplicates
https://bugs.launchpad.net/bugs/427488
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
