Bug 352316 - Context ID not passed to property_get commands
Summary: Context ID not passed to property_get commands
Status: NEW
Alias: None
Product: DLTK
Classification: Technology
Component: Common-Debug (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: dltk.common-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-18 04:46 EDT by Julien Desgats CLA
Modified: 2011-07-19 04:35 EDT (History)
1 user (show)

See Also:

Attachments
Simple test file to reproduce bug (109 bytes, text/x-python)
2011-07-18 04:46 EDT, Julien Desgats CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Julien Desgats CLA 2011-07-18 04:46:49 EDT 
Created attachment 199813 [details]
Simple test file to reproduce bug

When a property is queried to the debugger engine, the command does not contain the property context. The command has the form "property_get -d <depth> -n <varname> -p 0 -i <id>" and the "-c" option is never passed.

According to the DBGp specification, the context parameter is optional and defaults to local context. So the context parameter should be included for querying variables outside the local scope.

An example to reproduce this bug is attached. Run it with the Python plugin: put a breakpoint inside the function and you will see that the local and global foo variables refer both to the local one in variables view.

This issue is present at least in DLTK 2 and 3 branches.