bogus OverflowError: python bug?

Duncan Grisby duncan-news at grisby.org
Fri Jun 11 12:04:48 CEST 2004


In article <vvaxc.6919$%r.94680 at nasal.pacific.net.au>,
 Luke  <luked at xplantechnology.com> wrote:

>Martin v. Löwis wrote:

>> There are other possible causes for bogus exceptions. A common one is 
>> that Python set an exception at some point, but the extension module
>> forgot to forward the exception. Then, the next time Python checks
>> for exceptions, it sees that there still is an exception pending, and
>> raises it. That exception will make no sense that that point, of course.
>
>Oh yes of course, thanks... this sounds to be more consistent with the 
>repeatability of the bogus exception.
>
>> Only a gdb session can tell what really happened.
>
>Ouch.  I might try searching the omniORB extension module for a 
>forgot-to-forward-exception bug first.

The best thing for you to do is to subscribe to the omniORB mailing
list, and post as much information as you can about the problem.
Please include the full traceback, and a log from omniORB run with
-ORBtraceLevel 25.

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --



More information about the Python-list mailing list