public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
* Launching the GDB debugger on the target when starting the debug  session.
@ 2007-08-18 13:09 Geert Vancompernolle
  2007-08-22 11:04 ` Dave Korn
  0 siblings, 1 reply; 4+ messages in thread
From: Geert Vancompernolle @ 2007-08-18 13:09 UTC (permalink / raw)
  To: Insight Foum

Hi,

Is it possible to launch the GDB server on the target the moment you 
press the "Run" button in Insight?

Currently, the GDB server always has to be started manually, preferably 
prior to launching the Insight debugger.

Would be handy if this could be done from within Insight.

If not possible now, it might be a handy feature for a future release.

Best rgds,

--Geert

^ permalink raw reply	[flat|nested] 4+ messages in thread

* RE: Launching the GDB debugger on the target when starting the debug  session.
  2007-08-18 13:09 Launching the GDB debugger on the target when starting the debug session Geert Vancompernolle
@ 2007-08-22 11:04 ` Dave Korn
  2007-08-22 15:41   ` Geert Vancompernolle
  0 siblings, 1 reply; 4+ messages in thread
From: Dave Korn @ 2007-08-22 11:04 UTC (permalink / raw)
  To: 'Geert Vancompernolle', 'Insight Foum'

On 18 August 2007 14:10, Geert Vancompernolle wrote:

> Hi,
> 
> Is it possible to launch the GDB server on the target the moment you
> press the "Run" button in Insight?
> 
> Currently, the GDB server always has to be started manually, preferably
> prior to launching the Insight debugger.
> 
> Would be handy if this could be done from within Insight.
> 
> If not possible now, it might be a handy feature for a future release.


  It's tricky though.  There's no standard way to "launch a process X on a remote
machine Y".  Did you have a mechanism in mind?

  BTW, this kind of question makes sense to discuss on the main gdb list.
Insight is a gui wrapper that drives an underlying instance of gdb debugger.  In
the case of hitting the 'run' button, it's just sending a 'run' command to the
gdb instance, and that's probably where you'd want to add the underlying
functionality.  There are a lot more people on the main gdb list, so you'd have a
better chance of a useful discussion.  GUI-only issues, otoh, are still best
posted here.


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Launching the GDB debugger on the target when starting the debug   session.
  2007-08-22 11:04 ` Dave Korn
@ 2007-08-22 15:41   ` Geert Vancompernolle
  2007-08-22 15:51     ` Dave Korn
  0 siblings, 1 reply; 4+ messages in thread
From: Geert Vancompernolle @ 2007-08-22 15:41 UTC (permalink / raw)
  To: Dave Korn; +Cc: 'Insight Foum'

Dave Korn wrote:
> On 18 August 2007 14:10, Geert Vancompernolle wrote:
>
>   
>> Hi,
>>
>> Is it possible to launch the GDB server on the target the moment you
>> press the "Run" button in Insight?
>>
>> Currently, the GDB server always has to be started manually, preferably
>> prior to launching the Insight debugger.
>>
>> Would be handy if this could be done from within Insight.
>>
>> If not possible now, it might be a handy feature for a future release.
>>     
>
>
>   It's tricky though.  There's no standard way to "launch a process X on a remote
> machine Y".  Did you have a mechanism in mind?
>
>   BTW, this kind of question makes sense to discuss on the main gdb list.
> Insight is a gui wrapper that drives an underlying instance of gdb debugger.  In
> the case of hitting the 'run' button, it's just sending a 'run' command to the
> gdb instance, and that's probably where you'd want to add the underlying
> functionality.  There are a lot more people on the main gdb list, so you'd have a
> better chance of a useful discussion.  GUI-only issues, otoh, are still best
> posted here.
>
>
>     cheers,
>       DaveK
>   

Hi Dave,

To answer your question regarding a mechanism I have in mind, I can tell 
you the following:

At the office, we're using the MontaVista DevRocket debugger 
environment.  Their 2.0 release was about the same as the current 
Insight wrt starting up a debug session.  You had to start the server on 
the target manually, then launch the debugger.

Now, with their newest release (DevRocket 5.0), they've changed this 
behaviour.  There's no need any more to start the GDB server 
separately.  It's done through the debugger GUI the moment you start 
your application on the debugger.

I don't know, however, how they were able to install such mechanism.


Regarding the location of my question, you're talking about the "main 
gdb list".  Could you point me to that list?  Then I can for sure pose 
my question over there.

Thanks!

-- 
Best rgds,

Geert

^ permalink raw reply	[flat|nested] 4+ messages in thread

* RE: Launching the GDB debugger on the target when starting the debug  session.
  2007-08-22 15:41   ` Geert Vancompernolle
@ 2007-08-22 15:51     ` Dave Korn
  0 siblings, 0 replies; 4+ messages in thread
From: Dave Korn @ 2007-08-22 15:51 UTC (permalink / raw)
  To: 'Geert Vancompernolle'; +Cc: 'Insight Foum'

On 22 August 2007 16:41, Geert Vancompernolle wrote:

> Dave Korn wrote:
>> On 18 August 2007 14:10, Geert Vancompernolle wrote:

>>> Is it possible to launch the GDB server on the target the moment you
>>> press the "Run" button in Insight?
>>> 
>>> Currently, the GDB server always has to be started manually, preferably
>>> prior to launching the Insight debugger.
>>> 
>>> Would be handy if this could be done from within Insight.

>>   It's tricky though.  There's no standard way to "launch a process X on a
>> remote machine Y".  Did you have a mechanism in mind?
>> 
>>   BTW, this kind of question makes sense to discuss on the main gdb list.

> To answer your question regarding a mechanism I have in mind, I can tell
> you the following:
> 
> At the office, we're using the MontaVista DevRocket debugger
> environment.  Their 2.0 release was about the same as the current
> Insight wrt starting up a debug session.  You had to start the server on
> the target manually, then launch the debugger.
> 
> Now, with their newest release (DevRocket 5.0), they've changed this
> behaviour.  There's no need any more to start the GDB server
> separately.  It's done through the debugger GUI the moment you start
> your application on the debugger.
> 
> I don't know, however, how they were able to install such mechanism.

  Well, it's presumably because they get to control configuration of the target,
and they can set up an account on the machine so that the debug host can log in
as if it were a user.  That works for one dev system from one supplier that's
based on linux (and so supports network login, ftp, rcmds etc) but it would be
hard to make generic.


> Regarding the location of my question, you're talking about the "main
> gdb list".  Could you point me to that list?  Then I can for sure pose
> my question over there.

  Replace 'insight@' with 'gdb@' in the list address and you're there!  For the
homepage:

http://sourceware.org/gdb

To subscribe to (any of) the list(s) or view the archives:

http://sourceware.org/gdb/mailing-lists/


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2007-08-22 15:51 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-08-18 13:09 Launching the GDB debugger on the target when starting the debug session Geert Vancompernolle
2007-08-22 11:04 ` Dave Korn
2007-08-22 15:41   ` Geert Vancompernolle
2007-08-22 15:51     ` Dave Korn

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).