Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: "Gruenhagen, Andreas" <andreas.gruenhagen@sap.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Detecting when gdb is attached
Date: Thu, 04 Nov 2010 16:19:00 -0000	[thread overview]
Message-ID: <AANLkTikLJbTnZOS20-Fpgyp_H27pdX7+T70r06eYcs+H@mail.gmail.com> (raw)
In-Reply-To: <372C920CA9488345BDECCD4B62FF71D00F717855E5@DEWDFECCR08.wdf.sap.corp>

On Thu, Nov 4, 2010 at 6:40 AM, Gruenhagen, Andreas
<andreas.gruenhagen@sap.com> wrote:
> Dear gdb community,
> I'm developing an application which cannot be started from within the gdb. Therefore, I have the start the application and attach the gdb afterwards. In some cases it would be nice to have the application wait in a spin loop until the debugger is attached. Is there any way of accomplishing such a thing?
> I certainly can program the spin loop myself, attach the debugger, and then manually change a variable from within the debugger to end the loop. But, obviously, this is not an elegant solution (lots of manual work, code has to be changed and it has to be recompiled,and eventually, I might forget to delete the spin loop after debugging).
>
> I thought of having some sort of action which is executed when the gdb is attached and detached, this could be for example used to switch a static flag in the debugee.
> Is something like this possible ?

Hi.  I'm not sure I understand the issue.
I can't tell if adding code to the app to detect when gdb has attached
is ok or not.
[e.g. "it would be nice to have the application wait in a spin loop
until the debugger is attached. Is there any way of accomplishing such
a thing?" versus "I might forget to delete the spin loop"]

Guessing, what if you passed a flag to the app to enable the spin
loop?  Then you can keep the spin loop and only specify the flag when
you want to attach with gdb.


  reply	other threads:[~2010-11-04 16:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-04 13:40 Gruenhagen, Andreas
2010-11-04 16:19 ` Doug Evans [this message]
2010-11-04 17:26 ` paawan oza
2010-11-10 14:57 ` Steffen Dettmer

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=AANLkTikLJbTnZOS20-Fpgyp_H27pdX7+T70r06eYcs+H@mail.gmail.com \
    --to=dje@google.com \
    --cc=andreas.gruenhagen@sap.com \
    --cc=gdb@sourceware.org \
    /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