| RE: [cdt-dev] RE:Error creating process while debugging with my targetspecific gdb |
Aparna, I saw that Mikhail had fixed this piece of code in CStackFrame.java. I have attached the file along with this email. You can see if your CStackFrame.java has the isDisposed () method / flag. The code is available in the package "org.eclipse.cdt.debug.internal.core.model". Thanks, - Bala -----Original Message----- From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Aparna Argade Sent: Tuesday, December 13, 2005 12:00 PM To: cdt-dev@xxxxxxxxxxx Subject: [cdt-dev] RE:Error creating process while debugging with my targetspecific gdb Hi Bala, I am using cdt 3.0.1 and eclipse sdk 3.1.1. But still I am getting the error. Is there any way to check CStackFrame flag? Thanks, Aparna ------------------------------ >Aparna, > > Please refer to the following response by Mikhail. You are referring >to the same problem. > >Thanks, >Bala >Bala, > >The problem has been fixed for 3.0.1 (see >https://bugs.eclipse.org/bugs/show_bug.cgi?id=109785 ><https://bugs.eclipse.org/bugs/show_bug.cgi?id=109785> ). When you step >out of a function, the platform schedules a job to refresh the Variables >view for the old stack frame. The stack frame has gone on the target by >the time when the job starts running. This doesn't happen every time >because of the timing issues. Unfortunately, we don't have control on >this type of jobs (hopefully, it will be possible in Eclipse 3.2), so we >can't prevent it from running. But we added a flag to the CStackFrame >class to indicate that it has been disposed. > >Mikhail _______________________________________________ cdt-dev mailing list cdt-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/cdt-dev
Attachment:
CStackFrame.java
Description: CStackFrame.java