Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Stan Shebs <stan@codesourcery.com>
Cc: Aravinda <aravindakidambi@gmail.com>, gdb@sourceware.org
Subject: Re: GDB library to insert and delete watchpoints
Date: Fri, 04 Dec 2009 16:38:00 -0000	[thread overview]
Message-ID: <20091204163819.GC2903@adacore.com> (raw)
In-Reply-To: <4B18CD92.8000302@codesourcery.com>

> It just so happens that CodeSourcery recently did this for a
> customer that was using a debugging stub that ran as one of several
> threads in the application.

This reminds me of another interesting approach that one of our
customers implemented.  In their setup, the software was hooked to
a hardware that needed some trajectory info sent at a given frequency
(about 10Hz IIRC).  The problems started when they were trying to
debug problems, because the debugger would stop all threads. So,
what they did was implement their own gdbserver stub, embedded in
their application.  That stub would control start/stop etc in a way
that the motion threads remain alive and kicking while the rest of
the application is being inspected... AFAIK, they made it work
(this was on Windows).

-- 
Joel


      parent reply	other threads:[~2009-12-04 16:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <26eb53620911301516x68ccc0edkf64ba2951c8ce3a3@mail.gmail.com>
     [not found] ` <26eb53620911301518y13e64bc0g95c6fe3c7b18b0c@mail.gmail.com>
2009-12-01  5:44   ` Paul Pluzhnikov
2009-12-01 18:08     ` Dave Korn
2009-12-01 21:14   ` Jan Kratochvil
2009-12-04  8:51   ` Stan Shebs
2009-12-04 16:21     ` Aravinda
2009-12-04 17:11       ` Jan Kratochvil
2009-12-07 21:30         ` Aravinda
2009-12-04 16:38     ` Joel Brobecker [this message]

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=20091204163819.GC2903@adacore.com \
    --to=brobecker@adacore.com \
    --cc=aravindakidambi@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=stan@codesourcery.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