| Summary: | Process information of second PTP debug session messed up with process information of first debug session. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Tools] PTP | Reporter: | Xuan Chen <xuanchen> | ||||
| Component: | Debug UI | Assignee: | Project Inbox <ptp-inbox> | ||||
| Status: | RESOLVED INVALID | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | g.watson, yanma | ||||
| Version: | 5.0 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Xuan Chen
Created attachment 181122 [details]
screen capture
This is working as expected. Only one debug session is active at a time. If you select the other job in the Parallel Debug view, it will become active and you will see the stack frames. (In reply to comment #2) > This is working as expected. Only one debug session is active at a time. If you > select the other job in the Parallel Debug view, it will become active and you > will see the stack frames. Hi Greg, I may be wrong. But I do not think it is working as expected. You may tell from the attached screen capture that the stack information for program "hello1" is under the name of another program "testLB". I agree the screen capture doesn't look correct, but I'm unable to reproduce. I've started three debug sessions and I can switch between each. There is no mixing of information that I can see. Have you tried this on the latest HEAD code recently? (In reply to comment #4) > I agree the screen capture doesn't look correct, but I'm unable to reproduce. > I've started three debug sessions and I can switch between each. There is no > mixing of information that I can see. Have you tried this on the latest HEAD > code recently? Hi Greg, I am using PTP5.0 on Linux 86 servers. Did you make any updates on PTP5.0 as well as 4.0? I re-tested it on my settings and the problem still exists. Thanks. I'm trying this on CVS HEAD (5.0). Have you updated recently? (In reply to comment #6) > I'm trying this on CVS HEAD (5.0). Have you updated recently? Hi, I did not find this problem in latest HEAD. I think this bug should have been fixed by updates. Thanks. |