[New-bugs-announce] [issue15005] trace corrupts return result on chained execution

anatoly techtonik report at bugs.python.org
Tue Jun 5 16:40:11 CEST 2012

New submission from anatoly techtonik <techtonik at gmail.com>:

This code dumps a lot of internal source code info when executed with trace as:

python -m trace --trace file2.py

import subprocess

def ret():
  output = subprocess.check_output(['hg', 'id', '-nib'])
  print( output )
  print( output )
  print( output.strip() )
  print( output.strip().split() )


Normally, the last line of the output is:
['e67793ec2995+', '2162+', 'default']

But during trace call it is:
['subprocess.py(1180):', '_dup2(errwrite,', '2)', '---', 'modulename:', 'subprocess,', 'funcname:', '_dup2', 'subprocess.py(1174):', 'if', 'a', '==', 'b:', 'subprocess.py(1176):', 'elif', 'a', 'is', 'not', 'None:', 'subprocess.py(1184):', 'closed', '=', '{', 'None', '}',

files: file2.py
messages: 162347
nosy: techtonik
priority: normal
severity: normal
status: open
title: trace corrupts return result on chained execution
versions: Python 2.7
Added file: http://bugs.python.org/file25832/file2.py

Python tracker <report at bugs.python.org>

More information about the New-bugs-announce mailing list