| Summary: | Issue terminating a 6.8 gdb session on Windows | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Tools] CDT | Reporter: | John Cortell <john.cortell> | ||||
| Component: | cdt-debug-dsf-gdb | Assignee: | Project Inbox <cdt-debug-dsf-gdb-inbox> | ||||
| Status: | CLOSED INVALID | QA Contact: | Marc Khouzam <marc.khouzam> | ||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | pawel.1.piech | ||||
| Version: | 7.0 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
John Cortell
Created attachment 168594 [details]
screenshot
Do you have the latest debug platform checked out? This may be related to a fix I have committed for Bug 264895, which requires the latest platform (RC1) (In reply to comment #2) > Do you have the latest debug platform checked out? This may be related to a > fix I have committed for Bug 264895, which requires the latest platform (RC1) Marc, I updated to RC1 this morning and I'm still seeing the issue. (In reply to comment #3) > (In reply to comment #2) > > Do you have the latest debug platform checked out? This may be related to a > > fix I have committed for Bug 264895, which requires the latest platform (RC1) > > Marc, I updated to RC1 this morning and I'm still seeing the issue. I'm installing RC1 now. With M7 and the platform's debug plugins, I didn't see the problem. How do you reproduce it? Cygwin or MinGw? (In reply to comment #4) > I'm installing RC1 now. With M7 and the platform's debug plugins, I didn't see > the problem. How do you reproduce it? Cygwin or MinGw? I don't see it, even with RC1 and no platform plugins checked-out. Let me know how you do it, since it happens 100% of the time for you. I updated last night and no longer see the issue this morning. I was seeing it on both my office machine and home machine. I'm currently on my home machine. I believe it's still happening on my work machine. So, if I'm lucky and remember, I'll see what deltas I'm missing and that might reveal what the cause was. I looked at the recent CVS log and the only change I thought could be responsible made no difference when I reverted it. Oh well. I'm going to mark this resolved. I switched to using the platform debug core and ui plugins from M7 and I can reproduce the problem. I use the ones from RC1 and I can't reproduce the problem. I'm not sure how I was still seeing the problem when I moved to RC1, but lets chuck it up to user/configuration confusion. (In reply to comment #7) > I switched to using the platform debug core and ui plugins from M7 and I can > reproduce the problem. I use the ones from RC1 and I can't reproduce the > problem. I'm not sure how I was still seeing the problem when I moved to RC1, > but lets chuck it up to user/configuration confusion. Good news. Confirmed that my work machine has the M7 platform debug ui plugin in the workspace. I removed it and the problem went away. Mystery solved. (In reply to comment #9) > Confirmed that my work machine has the M7 platform debug ui plugin in the > workspace. I removed it and the problem went away. Mystery solved. When I saw an update on this bug in my inbox, I got worried for a second :-) I'm glad (very) this was a false alarm. Should we mark the bug as INVALID? (since there is no milestone and no assignee) (In reply to comment #10) > (In reply to comment #9) > > Confirmed that my work machine has the M7 platform debug ui plugin in the > > workspace. I removed it and the problem went away. Mystery solved. > > When I saw an update on this bug in my inbox, I got worried for a second :-) > I'm glad (very) this was a false alarm. > > Should we mark the bug as INVALID? (since there is no milestone and no > assignee) Done. |