RE: [cdt-dev] Error creating process while debugging with my targetspeci

["Krithivasan, Balasubramaniyan (STSD)" <balasubramaniyan.krithivasan@xxxxxx>]

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

 

 

 


________________________________

From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Aparna Argade
Sent: Tuesday, December 13, 2005 11:45 AM
To: cdt-dev@xxxxxxxxxxx
Subject: [cdt-dev] Error creating process while debugging with my
targetspecific gdb 



Hi,

I have successfully extended MBS for a target specific gcc. Now I am
integrating my target specific gdb. When I try to debug my program
through my gdb, I get a message box "Execution is suspended because of
error" with Details as "Error creating process
/cygdrive/d/testwkspace/demo3/Debug/demo3.out, (error 193)".

The Console shows following text-

mi_cmd_stack_list_frames: No stack.

No symbol "auto" in current context.

Error creating process /cygdrive/d/testwkspace/demo3/Debug/demo3.out,
(error 193)

 

What could be the reason for this error? 

Note: If I debug the same output file (demo3.out) from the command
prompt then debugging happens properly. 

 

To integrate my target specific gdb, I've done following steps.

1.	I have extended debug.core.CDebugger point. Created a class
which extends from GDBDebugger. This class doesn't do anything special,
just calls respective 'super' methods. 
2.	Extended debug.ui.CDebuggerPage point. Created a class which
extends from GDBDebuggerPage. This class overrides initializeFrom
method, in which I set my gdb's name in text box on the page. Also I
created a file to read gdb commands like target sim, load, b main. 
3.	I have extended my plugin class from MIPlugin. This class
contains default implementation of plugin class. 

 

Is my approach correct? 

Actually I could not find much help for extending debugger. Is there any
document/reference which explains the flow?

 

Please help.

Thanks & Regards,

Aparna