RE: [cdt-debug-dev] Re: Debugging executables with no project

["Alexiev, Dobrin" <dalexiev@xxxxxx>]

Here is what I found with only 2-3 hours so far: 

1. CDebugTarget.initializeModuleManager()
- add "if( getExecFile() != null || )" in the beginning. 

2. CSourcePathComputerDelegate.computeSourceContainers
- change "if ( projectName != null ) {" to 
	"if ( projectName != null && projectName.length() > 0) {"

Here are some assumptions: 
1. Our launch delegate does NOT set ATTR_PROJECT_NAME and
ATTR_PROGRAM_NAME. 
2. We still haven't implemented all of the CDI yet. 
3. I've done very little testing. 
4. Our LaunchConfigurationTabGroup didn't use CMainTab since that shows
error if you don't specify a project or program. 

I'll try to do spend more time on this in the next few days. 
Thanks
Dobrin

-----Original Message-----
From: cdt-debug-dev-bounces@xxxxxxxxxxx
[mailto:cdt-debug-dev-bounces@xxxxxxxxxxx] On Behalf Of Mikhail
Khodjaiants
Sent: Thursday, November 17, 2005 10:32 AM
To: CDT Debug developers list
Subject: Re: [cdt-debug-dev] Re: Debugging executables with no project

Great. Did you have to make hacks in the CDT code?

----- Original Message ----- 
From: "Alexiev, Dobrin" <dalexiev@xxxxxx>
To: "CDT Debug developers list" <cdt-debug-dev@xxxxxxxxxxx>
Sent: Thursday, November 17, 2005 10:20 AM
Subject: RE: [cdt-debug-dev] Re: Debugging executables with no project


> Thanks Mikhail, 
> I hope the next week I can pinpoint the changes needed in CDT to
> accommodate the project-less and program-less debugging. 
> Right now I have a CDI debugger that is not GDB with its own launch
> configuration type. 
> Dobrin
> 
> -----Original Message-----
> From: cdt-debug-dev-bounces@xxxxxxxxxxx
> [mailto:cdt-debug-dev-bounces@xxxxxxxxxxx] On Behalf Of Mikhail
> Khodjaiants
> Sent: Wednesday, November 16, 2005 7:23 PM
> To: CDT Debug developers list
> Subject: Re: [cdt-debug-dev] Re: Debugging executables with no project
> 
> Dobrin,
> 
> I'll try to answer to some of your questions. See my comments inline.
> 
> ----- Original Message ----- 
> From: "Alexiev, Dobrin" <dalexiev@xxxxxx>
> To: <cdt-debug-dev@xxxxxxxxxxx>
> Sent: Wednesday, November 16, 2005 5:49 PM
> Subject: [cdt-debug-dev] Re: Debugging executables with no project
> 
> 
>> Hi Ken,
>>
>> Great job! I really like your proposal.
>>
>> We were just about to start doing something similar and I am so glad
>> that you are already done it and you are working with CDT to get it
in
>> the main stream.
>>
>> Here are my notes for the project-less proposal and the advanced
>> breakpoints you mentioned in the power point slides:
>>
>> Project-less debugging
>>
>> 1. I noticed that making a really project-less debugging is not
>> considered. What are the real problems with that? I was going to
>> investigate that too because we have use cases in which the user just
>> want to do low level debugging - stepping in assembly, stack frame
> with
>> only assembly addresses, opening register and memory windows, having
> the
>> console connected so they can control the debugging and do Std IO
>> operations. None of these require OUT file or source files debugging.
> I
>> was about to investigate what are the current limitations in CDT to
>> achieve this but after I saw your comments looks like you already
have
>> done some investigation. Is it something with the platform that has
to
>> change or it is only CDT? Is anyone interested in achieving real
>> project-less debugging?
> 
> Indeed, in this case there is no need to have a project or an
executable
> for 
> debugging, assuming you are attaching to a running process. The
problem
> is 
> that currently the CDT debugger uses the executable to get the address

> 
> factory. It is also used to create address breakpoints. Both problems
> are 
> solvable in the CDT frame. And I am definitely interested to make the
> CDT 
> debugger cleaner.
> 
>> 2. How does this integrate with different CDI debuggers? We are in
>> a process of making our backend a CDI debugger and we have our launch
>> type, lunch delegate, CDebugger, etc. Will you implementation hook up
>> with a non GDB debuggers nicely?
> 
> All manipulations with projects are done above the CDI level.
> Executables 
> are used to create sessions, but null can be passed to 
> "createAttachSession".
> 
>> You mentioned that the last step of the
>> debugger is creating a launch configuration. Is that configurable -
> can
>> the user create our debugger's launch configuration?
>> 3. What is the plan of getting this is CDT - is there attached
>> patch we can look at?
>>
> 
> Assuming the problems with address factories and address breakpoints
are
> 
> fixed, I would prefer to have a special launch configuration type for
> this 
> type of debug sessions.
> 
>> Breakpoint extensions
>>
>> 1. For the advanced breakpoint you mentioned that one action is to
>> execute a script. What scrip is that? Is it backend script only or it
> is
>> something more generic? How will this fits with CDT?
>> 2. What are the plans for making the implementation of the advanced
>> breakpoints available?
>>
>> Regards
>>
>> Dobrin Alexiev
>>
>> Texas Instruments
>>
>>  _____
>>
>> Title: Debugging executables with no project
>>
>> Hi,
>>
>> At the recent CDT Contributors Summit I presented a proposal for some
>> additions to let you easily debug executables even if you don't have
a
>> project that builds them.
>>
>> Doug had posted the slides here:
>>
>>
>
http://download.eclipse.org/tools/cdt/docs/summit2005/Debugger_Features.
>> ppt
>>
>
<http://download.eclipse.org/tools/cdt/docs/summit2005/Debugger_Features
>> .ppt>
>>
>> and I've just attached a more detailed description of our proposal
to:
>>
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=39640
>>
>> Please take a look and send me any feedback, comments, or questions.
>>
>> Thanks,
>>
>> Ken Ryall
>> Nokia Developer Platform Tools
>>
>> 
> 
> _______________________________________________
> cdt-debug-dev mailing list
> cdt-debug-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
> _______________________________________________
> cdt-debug-dev mailing list
> cdt-debug-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev