Bugzilla – Full Text Bug Listing
| Summary: | Context ID not passed to property_get commands | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Technology] DLTK | Reporter: | Julien Desgats <jdesgats> | ||||
| Component: | Common-Debug | Assignee: | dltk.common-inbox <dltk.common-inbox> | ||||
| Status: | NEW --- | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | P3 | CC: | contact | ||||
| Version: | 3.0 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
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.