public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Cedric Roux <cedric.roux@acri-st.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Getting gcov's output when the program is killed
Date: Fri, 26 Feb 2010 17:52:00 -0000	[thread overview]
Message-ID: <4B87A56D.1090606@acri-st.fr> (raw)
In-Reply-To: <87ljeg5n2c.fsf@gnu.org>

Ludovic Courtès wrote:
> Hello,
> 
> I’m doing test coverage on a daemon.  The daemon is tested by a script
> that launches it and eventually terminates it with kill(1).  However,
> the corresponding gcda files are not updated with actual coverage data.
> 
> How can gcov be told to flush its coverage data to disk when the program
> is killed?
> 
> Thanks,
> Ludo’.

maybe you can modify slightly your deamon, catch the signal
and do a "clean" exit by calling "exit" in the signal handler
or something?
And have a conditional in your code to include/exclude that
behavior depending if you compile with coverage or not.

  reply	other threads:[~2010-02-26 10:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-26 15:26 Ludovic Courtès
2010-02-26 17:52 ` Cedric Roux [this message]
2010-02-27  5:58 ` Ian Lance Taylor

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=4B87A56D.1090606@acri-st.fr \
    --to=cedric.roux@acri-st.fr \
    --cc=gcc-help@gcc.gnu.org \
    --cc=ludo@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).