public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: "Nik Shaylor" <ns@c7.org>
To: "Keith Seitz" <keiths@redhat.com>
Cc: insight@sourceware.org
Subject: Re: How to connect to running program via a serial port
Date: Mon, 14 Aug 2006 21:01:00 -0000	[thread overview]
Message-ID: <20934fa50608141401o7ac5a8dl71cc71b6957a17f@mail.gmail.com> (raw)
In-Reply-To: <44E0DFD8.5010208@redhat.com>

Hi Keith, Thanks for your message. Neither of these techniques seem to
work for me. If I open the console window and type "target remote
/dev/ttyS0" the program seems to lock up. (The windows are present,
but not responding to any input). If I do Open File->Target Settings
etc. still have to use the "Run" command and this always continues the
execution of the program which is just what I don't want it to do.

The only way I seems to get it to work is to start Insight running
before the program wants to start talking to the debugger. This does
not really work for me because I'm using the serial port for program
trace information as well so I just want to start the debugger when I
can see from the trace that the program has got into trouble.

Thanks,

Nik

On 8/14/06, Keith Seitz <keiths@redhat.com> wrote:
> Nik Shaylor wrote:
> > So with gdb I just type:
> >
> >   target remote /dev/ttyS0
> >
> > and I can start debugging the, already running, program via the serial
> > port.
> >
> > When I start Insight it thinks nothing is running and the only button
> > that works us the "Run" command. How can I start Insight ina mode
> > where it will thinks the program is already running?
>
> You have two options:
>
> 1) Open a console window and type your gdb command in
> 2) Open File->Target Settings..., and select "Remote/Serial", enter buad
> rate, com port. Use Run menu to attach to target. That should be all you
> need.
>
> [The Run button is a little more elaborate. In the target settings
> dialog, you can specify what the run button does by clicking "More
> options". Currently the run button will ALWAYS either "run" or
> "continue" the target.]
>
> Keith
>
>

  reply	other threads:[~2006-08-14 21:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-14 20:35 Nik Shaylor
2006-08-14 20:41 ` Keith Seitz
2006-08-14 21:01   ` Nik Shaylor [this message]
2006-08-14 21:04     ` Keith Seitz
     [not found]       ` <20934fa50608141410g6ad3fbeep98905eaf34335c75@mail.gmail.com>
2006-08-14 22:19         ` Keith Seitz
     [not found]           ` <20934fa50608141533g36faf06aq8e724c256495eb69@mail.gmail.com>
2006-08-14 22:41             ` Keith Seitz
2006-08-15  1:39       ` Dave Korn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20934fa50608141401o7ac5a8dl71cc71b6957a17f@mail.gmail.com \
    --to=ns@c7.org \
    --cc=insight@sourceware.org \
    --cc=keiths@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).