Bug 624630 - Allow starting a remote debugging session from the command line
Allow starting a remote debugging session from the command line
Status: RESOLVED FIXED
Product: nemiver
Classification: Other
Component: general
trunk
Other Linux
: Normal enhancement
: ---
Assigned To: Nemiver maintainers
Nemiver maintainers
:
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2010-07-17 18:25 UTC by Dodji Seketeli
Modified: 2010-10-13 19:17 UTC (History)
1 user (show)

See Also:
GNOME target: ---
GNOME version: ---


Attachments

Description Dodji Seketeli 2010-07-17 18:25:16 UTC
Right now it is not possible to start remote debugging from the command line. You are obliged to type the necessary parameters in the GUI. It would be nice to do that from the command line.
Comment 1 Dodji Seketeli 2010-10-03 15:18:06 UTC
I have started working on this feature and there is some preliminary support in the "remote-cmdline" branch accessible at http://git.gnome.org/browse/nemiver/log/?h=remote-cmdline

Basically you can now connect to a remote target using nemiver by doing:

nemiver --remote HOST:PORT <binary-program>

Nemiver will connect to the gdbserver running at IP address HOST (that could be a hostname too) and listening on PORT.
<binary-program> is a local copy of the binary program running on the remote host.

I still need to flesh out some things like restarting the inferior, or integrating with the session saving machinery so that when you do nemiver --last, it reconnects to the same remote you were connected to previously.
Comment 2 Dodji Seketeli 2010-10-03 16:57:12 UTC
Small typo. The correct way of invoking Nemiver here is:

nemiver --remote=HOST:PORT <binary-program>

(do not forget the '=' after the --remote).

Some code got added to the branch to catch cases where the user issues a wrong command line and display an error message instead of going bonker.
Comment 3 Dodji Seketeli 2010-10-13 19:17:07 UTC
This is now fixed since the remote-cmdline feature branch has been merge into master. This is going to be available in Nemiver 0.8.

Note You need to log in before you can comment on or make changes to this bug.