[ python-Bugs-1117670 ] profiler: Bad return and Bad call errors with exceptions
SourceForge.net
noreply at sourceforge.net
Sat Oct 8 09:05:40 CEST 2005
Bugs item #1117670, was opened at 2005-02-07 15:50
Message generated for change (Comment added) made by spiv
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1117670&group_id=5470
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Python Library
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Matthew Mueller (donut)
Assigned to: Nobody/Anonymous (nobody)
Summary: profiler: Bad return and Bad call errors with exceptions
Initial Comment:
I ran into a weird error when trying to profile a test
script of mine:
AssertionError: ('Bad call', ('', 0, 'encode'))
I managed to whittle it down to some minimal test
cases, which are attached (although the errors they
generate are slightly different.)
$ python-cvs -m profile profile_badcall.py
Traceback (most recent call last):
[snipped ...]
File
"/home/donut/usr64/python/lib/python2.5/profile.py",
line 444, in runctx
exec cmd in globals, locals
File "<string>", line 1, in ?
File "profile_badcall.py", line 10, in ?
os.path.join("C",'b')
File
"/home/donut/usr64/python/lib/python2.5/posixpath.py",
line 56, in join
def join(a, *p):
File
"/home/donut/usr64/python/lib/python2.5/profile.py",
line 228, in trace_dispatch_i
if self.dispatch[event](self, frame, t):
File
"/home/donut/usr64/python/lib/python2.5/profile.py",
line 285, in trace_dispatch_call
assert (self.cur is None or AssertionError: ('Bad call', ('profile_badcall.py', 2,
'trier'))
$ python-cvs -m profile profile_badreturn.py
Traceback (most recent call last):
[snipped...]
File
"/home/donut/usr64/python/lib/python2.5/profile.py",
line 444, in runctx
exec cmd in globals, locals
File "<string>", line 1, in ?
File
"/home/donut/usr64/python/lib/python2.5/profile.py",
line 228, in trace_dispatch_i
if self.dispatch[event](self, frame, t):
File
"/home/donut/usr64/python/lib/python2.5/profile.py",
line 312, in trace_dispatch_return
assert frame is self.cur[-2].f_back, ("Bad return",
self.cur[-3])
AssertionError: ('Bad return', ('profile_badreturn.py',
1, 'trier'))
The errors occur in python CVS as of 20050206 and
python 2.4, but not in python 2.3.4.
OS: debian sid (3.1)
Arch: amd64
----------------------------------------------------------------------
Comment By: Andrew Bennetts (spiv)
Date: 2005-10-08 17:05
Message:
Logged In: YES
user_id=50945
I still see this in current python 2.4, but not in current
python CVS.
Also, hotshot seems to work ok in 2.4 and CVS.
OS: ubuntu breezy (5.10)
Arch: i386
----------------------------------------------------------------------
Comment By: Gary Oberbrunner (garyoberbrunner)
Date: 2005-03-09 14:35
Message:
Logged In: YES
user_id=417980
Is there any news on this bug? It is possibly preventing
scons (http://scons.org) from being profiled on python 2.4
-- we get the same errors as above. Test case is too large
to include here, but please email me with any news if
possible! Would be glad to test a fix.
-- Gary
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1117670&group_id=5470
More information about the Python-bugs-list
mailing list