Re: Getting gcov's output when the program is killed

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Ian Lance Taylor <iant@xxxxxxxxxx>
Subject: Re: Getting gcov's output when the program is killed
From: ludo@xxxxxxx (Ludovic Courtès)
Date: Sun, 28 Feb 2010 18:46:32 +0100
Cc: gcc-help@xxxxxxxxxxx
In-reply-to: <mcrmxyvyeed.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> (Ian Lance Taylor's message of "Fri, 26 Feb 2010 11:40:10 -0800")
References: <87ljeg5n2c.fsf@xxxxxxx> <mcrmxyvyeed.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)

Hi,

Thanks for your suggestions.  Indeed, catching the signal and exiting
gracefully is all it takes to get the gcda files updated.

Ludo’.

References:
- Getting gcov's output when the program is killed
  - From: Ludovic Courtès
- Re: Getting gcov's output when the program is killed
  - From: Ian Lance Taylor

Prev by Date: Re: locale for Japanese Windows environment
Next by Date: Is it possible/desirable to avoid using collect2 on Solaris?
Previous by thread: Re: Getting gcov's output when the program is killed
Next by thread: gcc -D_GLIBCXX_FULLY_DYNAMIC_STRING
Index(es):
- Date
- Thread

[Index of Archives] [Linux C Programming] [Linux Kernel] [eCos] [Fedora Development] [Fedora Announce] [Autoconf] [The DWARVES Debugging Tools] [Yosemite Campsites] [Yosemite News] [Linux GCC]

Powered by Linux