* gcov status? Limitations?
@ 2001-10-09 11:53 nbecker
2001-10-10 11:10 ` Janis Johnson
0 siblings, 1 reply; 2+ messages in thread
From: nbecker @ 2001-10-09 11:53 UTC (permalink / raw)
To: gcc
I'm trying to use gcov with gcc-3.0.1 (i686-pc-gnu-linux). The
results I'm seeing make no sense at all.
What is the status of gcov? Is it supposed to work? Will it work
with g++? Will it work with inlined code? Templates?
I won't bore you all with lots of details, but just for a start:
4 int main (int argc, char** argv) {
2 rng_t rng;
2 double extraRemodDelay = 0.36;
2 if (argc > 1 && argv[argc-1] && argv[argc-1][0] != '-') {
###### yyin = fopen (argv[argc-1], "r");
###### InputFileName = argv[argc-1];
}
So main was called 4 times???? The next line 2 times??? The lines
marked ###### were supposedly not called? I know absolutely for sure
they were.
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.6 and Gnu Privacy Guard < http://www.gnupg.org/ >
mQGiBDZa9ZcRBACYGMoAmHIBUR19lDLZNJhgxGtqVchV7OiwniGIE0UpwRj08fDX
/KO7/cXgXDZqFEgHF98e6Gbm4efyyC7seP4Ye8Av3n8h8PMv307lQieJd5qQVvwx
vwJWGHsX1EOsv/Suzb2ZcYllU4dgrdBIkRLQ5tsJPiWtxjsfBsONGqWmIwCghmQA
GayzNTFUUy0JkGP8SEJRycED/0GvchcxrSnN0FDe5HqM2YzNOnQYGEasAgRSNoG7
O87uudA3j+Hh4GQSD7VgleYArCXqfaNd8pj+EY0ykGjcTJk07aAl+Ib8UrQ8eNk/
RON0+/ZRN6QGqte1lokR969AgVFDQaHV0IctElZdpRg+JbKUiBn3iYaY7xfYYr1z
M6l/A/4v7HkRTfoMsEae+vhuatmekXpV7rrcmhAjLdaUWbamNrkp7N6fnDMQcRjJ
DA/9VBV8qjokGu2PEj+HQGZb52y1+/S+wmUbKlS/EkYMME9gEDuUBFhHlC6xbYg1
akcddicTFhNHtwNQ9GFliIaJzU1Mt7LumB03/Cy0A9PouNUhv7QhTmVhbCBELiBC
ZWNrZXIgPG5iZWNrZXJAZnJlZC5uZXQ+iFcEExECABcFAjZa9ZcDCwQDBRUDAgYB
AxYCAQIXgAAKCRCtdGDCLVoO090GAJsFFd/nUF315R0Snt97iV39JP/OTQCeNAaU
5MsmAJHGFcXXj9AkMRoguzu5AQ0ENlr1pRAEAKpFYKuYC++L4RuzreeuKObO15SS
LXgUo0A/q9Hm3VFQw/FaWShBilVKjw6C7lUFnajx0uzy3EhczjitdcHewXyOH/9T
1WyqtiJG9CJTRgQkA1vDSgLBqLQ8so4saOF0bT/66iaiBE9Rbl1yRvjJh5lIULJr
BG2WhHfh/xWl2KS/AAMFBACQ/DrlJe9ooOQAuuUFK8P1A1t4zN5u9gvVMLhpxnr+
KYFa4+GdP3939lRTb7smtVxh9gote66kTmH776sqx7Sn8/Vsx5DOEKpikTlQ9IPR
mXu8Oe9skh+rJcOrjSOH7fSsYqqH7O1GArw0l82bBwA6Xz86vWfyHj/Slo0YXxey
QohGBBgRAgAGBQI2WvWlAAoJEK10YMItWg7TDiEAn3kIiU3z9lbtF4UexjL8zWIv
QszbAJ4om+wo1penO8/y9uI0UOgJQZUtJg==
=Q5Ab
-----END PGP PUBLIC KEY BLOCK-----
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: gcov status? Limitations?
2001-10-09 11:53 gcov status? Limitations? nbecker
@ 2001-10-10 11:10 ` Janis Johnson
0 siblings, 0 replies; 2+ messages in thread
From: Janis Johnson @ 2001-10-10 11:10 UTC (permalink / raw)
To: nbecker; +Cc: gcc
On Tue, Oct 09, 2001 at 02:53:39PM -0400, nbecker@fred.net wrote:
> I'm trying to use gcov with gcc-3.0.1 (i686-pc-gnu-linux). The
> results I'm seeing make no sense at all.
>
> What is the status of gcov? Is it supposed to work? Will it work
> with g++? Will it work with inlined code? Templates?
>
> I won't bore you all with lots of details, but just for a start:
>
> 4 int main (int argc, char** argv) {
> 2 rng_t rng;
>
> 2 double extraRemodDelay = 0.36;
>
> 2 if (argc > 1 && argv[argc-1] && argv[argc-1][0] != '-') {
> ###### yyin = fopen (argv[argc-1], "r");
> ###### InputFileName = argv[argc-1];
> }
>
> So main was called 4 times???? The next line 2 times??? The lines
> marked ###### were supposedly not called? I know absolutely for sure
> they were.
3.0.1 gcov is supposed to work with C++, but it isn't tested and there
could well be problems.
See http://gcc.gnu.org/bugs.html for information about reporting bugs in
GCC. Specific problems with test cases are more likely to lead to fixes
or to better documentation about limitations.
Janis
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2001-10-10 11:10 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-10-09 11:53 gcov status? Limitations? nbecker
2001-10-10 11:10 ` Janis Johnson
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).