[cdt-dev] AW: Command factory extension and bug #115804

["Ploett, Norbert" <norbert.ploett@xxxxxxxxxxx>]

Hi Mikhail,
 
I am trying to do remote debugging (gdbserver debugger) with CDT HEAD
but when I start the session it fails immediately with an error
messagebox:

Execution is suspended because of error.
  Error creating process
/cygdrive/d/Projekt/RTP/ws-committer-debug/test/Debug/aaa.exe, (error 5)

When I look into the trace of the gdb commands and compare with CDT
3.0.2(RC0) there are some differences but the crucial one seems to be
that 3.0.2 is using -exec-continue while HEAD is using -exec-run to
start after all the preliminaries were done.
Something got messed up here and I am not sure whether it has something
to do with the quick fix to make the "Command Set" option available for
the gdbserver debugger.

Pse look into it.

Thanks,


Norbert

________________________________

Von: Mikhail Khodjaiants [mailto:mikhailk@xxxxxxx] 
Gesendet: Mittwoch, 8. Februar 2006 18:52
An: Ploett, Norbert
Betreff: Re: Command factory extension and bug #115804


Done. 
GDBServerDebuggerPage now extends StabdardGDBdebuggerPage.
I also registered the standard command factory for this debugger type.
 
Mikhail



	----- Original Message ----- 
	From: Ploett, Norbert <mailto:norbert.ploett@xxxxxxxxxxx>  
	To: Mikhail Khodjaiants <mailto:mikhailk@xxxxxxx>  
	Sent: Wednesday, February 08, 2006 9:12 AM
	Subject: AW: Command factory extension and bug #115804

	That's fine, just drop me a note when you're done.
	 
	 
	Norbert

________________________________

	Von: Mikhail Khodjaiants [mailto:mikhailk@xxxxxxx] 
	Gesendet: Mittwoch, 8. Februar 2006 14:52
	An: Ploett, Norbert
	Betreff: Re: Command factory extension and bug #115804
	
	
	Hi Norbert,
	 
	Sorry, I should have realized that you are using gdbserver. My
fault. 
	I'll add the UI for command factories to the gdb sever page.
	 
	Thanks,
	Mikhail

		----- Original Message ----- 
		From: Ploett, Norbert
<mailto:norbert.ploett@xxxxxxxxxxx>  
		To: Mikhail Khodjaiants <mailto:mikhailk@xxxxxxx>  
		Sent: Wednesday, February 08, 2006 8:21 AM
		Subject: AW: Command factory extension and bug #115804

		Hi Mikhail,
		 
		implementing a new command factory and registering it
via the extension point worked fine. When trying to set up a test case I
ran into a problem:
		 
		All my examples for OSes which allow thread names are
for non-Posix (non-Cygwin, non-Linux), so I am always working on
embedded targets and connect with the gdbserver debugger. This debugger
does not (yet?) have the "GDB command set" combo. 
		The gdb/mi (new) debugger, on the other hand, does not
have the remote debugging facility.
		 
		How do I resolve this?
		Wait for gdb/mi debugger to learn remote debugging?
		Wait until the gdbserver debugger also implements the
"GDB command set" selecting capability?
		 
		Do you have any suggestions resp. what are your plans?
		 
		 
		Norbert

________________________________

		Von: Mikhail Khodjaiants [mailto:mikhailk@xxxxxxx] 
		Gesendet: Dienstag, 7. Februar 2006 00:41
		An: Ploett, Norbert
		Betreff: Command factory extension and bug #115804
		
		
		Hi Norbert,
		 
		I have added a new extension point that allows to
contribute a command factory (see my posting to the mailing list). Can
you, please, try it to fix
https://bugs.eclipse.org/bugs/show_bug.cgi?id=115804. 
		As far as I understand, all you need to do is to extend
the "CommandFactory" class by overwriting the "createCLIInfoThreads"
method. You can use "StandardWinCommandFactory" as an example.
		I would really appreciate your comments.
		 
		Thank you,
		Mikhail