RE: [cdt-dev] Fwd:Nacl-gdb and eclipse cdt integration

[Marc Khouzam <marc.khouzam@xxxxxxxxxxxx>]

It would be nice to make life easier for those people.
 
> 1) set the path to sel_ldr as the "C/C++ Application" on the main tab
> of the debug configuration dialog

This seems to require user input to know the proper path for that
developer's env

> 2) add any arguments you want to pass to sel_ldr (-d is implied when
> you start under gdb) and your nexe on the arguments tap

Here too.

> 3) create a command file to tell gdb to load your nexe. Mine only has
> 1 line, e.g:
> nacl-file hw.nexe

I guess this could be unified with the second part of point 2) and
we could tell gdb to load the file automatically.

> 4) on the debugger tab, set the path to nacl64-gdb in the "GDB
> debugger" field and your file in the "GDB command file" field

If we could automatically put the string 'nacl64-gdb' instead
of 'gdb'.  Could be done by solving 
Bug 120162 Allow to specify the default version of gdb

I guess the value of some support for this is to avoid the user
having to do point 3).

It probably wouldn't be too hard to have an extension point
like you suggest (I'm not sure what you guys did for the
managed build).  However, would the user have to define the entire
gdb startup sequence, which is not trivial, our would the user
simply add certain launch commands, like for Harware debugging.
The tricky thing for the latter may be to know the proper place 
to run those extra commands, during our launch sequence.

Marc




> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx 
> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer
> Sent: Friday, July 02, 2010 10:35 AM
> To: CDT General developers list.
> Subject: [cdt-dev] Fwd:Nacl-gdb and eclipse cdt integration
> 
> Hey gang, here is another example of using our debug framework for a
> different debugger set up. This is for Google's Native Client API
> which lets you download and run native code in a browser in a secure
> context.
> 
> I've seen this a couple of times now, Android also has some special
> commands to run to get going. How much work is it to create a simple
> launch configuration type that automates this? I'm thinking this could
> be something like what we've done with the managed build. We should be
> able to define gdb start-up as a simple extension point with maybe a
> little code. Any thoughts on that?
> 
> Thanks,
> Doug.
> 
> ---------- Forwarded message ----------
> From: Derek Schuff <dschuff@xxxxxxxxxx>
> Date: Thu, Jul 1, 2010 at 12:19 PM
> Subject: Re: [native-client-discuss] Nacl-gdb and eclipse cdt 
> integration
> To: native-client-discuss@xxxxxxxxxxxxxxxx
> 
> 
> It's quite simple, really. You just create a new debug configuration
> in your project and do the following:
> 1) set the path to sel_ldr as the "C/C++ Application" on the main tab
> of the debug configuration dialog
> 2) add any arguments you want to pass to sel_ldr (-d is implied when
> you start under gdb) and your nexe on the arguments tap
> 3) create a command file to tell gdb to load your nexe. Mine only has
> 1 line, e.g:
> nacl-file hw.nexe
> 3) on the debugger tab, set the path to nacl64-gdb in the "GDB
> debugger" field and your file in the "GDB command file" field
> After that, you can just start the debug, which launches sel_ldr and
> your nexe. once it starts up you can add nacl breakpoints.
> 
> On Wed, Jun 30, 2010 at 8:12 PM, ensynk360 
> <ensynk360@xxxxxxxxx> wrote:
> >
> > That sounds very interesting. Can you share with us a bit more about
> > how you exactly set up your environment? (e.g. command init file)
> >
> > --
> > You received this message because you are subscribed to the 
> Google Groups "Native-Client-Discuss" group.
> > To post to this group, send email to 
> native-client-discuss@xxxxxxxxxxxxxxxx.
> > To unsubscribe from this group, send email to 
> native-client-discuss+unsubscribe@xxxxxxxxxxxxxxxx.
> > For more options, visit this group at 
> http://groups.google.com/group/native-client-discuss?hl=en.
> >
> 
> --
> You received this message because you are subscribed to the Google
> Groups "Native-Client-Discuss" group.
> To post to this group, send email to 
> native-client-discuss@xxxxxxxxxxxxxxxx.
> To unsubscribe from this group, send email to
> native-client-discuss+unsubscribe@xxxxxxxxxxxxxxxx.
> For more options, visit this group at
> http://groups.google.com/group/native-client-discuss?hl=en.
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>