bug-cflow
[Top][All Lists]
Advanced

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

Re: [bug-cflow] bug-cflow Digest, Vol 34, Issue 4


From: Debajyoti Majumdar
Subject: Re: [bug-cflow] bug-cflow Digest, Vol 34, Issue 4
Date: Tue, 8 Dec 2015 00:07:20 +0530

No, a runtime profiler would generate
 only one path.
i need to generate all the possible paths that the program can possibly take.

On Mon, Dec 7, 2015 at 10:30 PM, <address@hidden> wrote:
Send bug-cflow mailing list submissions to
        address@hidden

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.gnu.org/mailman/listinfo/bug-cflow
or, via email, send a message with subject or body 'help' to
        address@hidden

You can reach the person managing the list at
        address@hidden

When replying, please edit your Subject line so it is more specific
than "Re: Contents of bug-cflow digest..."


Today's Topics:

   1. Re: bug-cflow Digest, Vol 34, Issue 2 (Sergey Poznyakoff)
   2. Re: Occurrence of a single function (Louis Bertrand)


----------------------------------------------------------------------

Message: 1
Date: Sun, 06 Dec 2015 20:00:39 +0200
From: Sergey Poznyakoff <address@hidden>
To: "Debajyoti Majumdar" <address@hidden>
Cc: address@hidden
Subject: Re: [bug-cflow] bug-cflow Digest, Vol 34, Issue 2
Message-ID: <address@hidden>

> Actually i am trying to do the exact same thing.
> Trying to depict the functions that are called in the loops in a
> better way.

How exactly?

Regards,
Sergey



------------------------------

Message: 2
Date: Sun, 06 Dec 2015 14:16:10 -0500
From: Louis Bertrand <address@hidden>
To: "address@hidden" <address@hidden>
Subject: Re: [bug-cflow] Occurrence of a single function
Message-ID: <address@hidden>
Content-Type: text/plain; charset="utf-8"

?Hi,
Wrong tool. Don't use a hammer when you need a screwdriver.?
I think you might need a runtime profiler.
Regards
?--Louis

Louis?Bertrand?<address@hidden>?
? Original Message ?

Actually i am trying to do the exact same thing.
Trying to depict the functions that are called in the loops in a better way.

Could you pls help me out in this aspect?

On Sat, Dec 5, 2015 at 10:30 PM, <address@hidden> wrote:

> Date: Sat, 5 Dec 2015 08:53:00 -0500
> From: Louis Bertrand <address@hidden>
> To: address@hidden
> Subject: Re: [bug-cflow] Occurrence of a single function
>
>
> > Date: Thu, 3 Dec 2015 14:20:18 +0530
> > From: Debajyoti Majumdar <address@hidden>
> > To: address@hidden
> > Subject: [bug-cflow] Occurrence of a single function
> >
> > Hello..
> > suppose in my c code if the same function is called again and again, the
> > output of cflow has only one occurrence of that particular code.
> > Why is it so?
> >
> > Eg: my test code is:
> > 1 #include<stdio.h>
> > 2 int main(){
> > 3 printf("hello ");
> > 4 printf("world");
> > 5
> > 6
> > 7
> > 8 return 0;
> > 9 }
> > ~
> > output is:
> >
> > main() <int main () at /home/deb/test.c:2>:
> > printf()
> >
> >
> > Shouldn't the ouput have 2 occurrences of printf()?
> > -------------- next part ???????
>
> cflow shows the caller-callee dependencies (see the documentation).
> What if your call to printf() was in a loop in which the number of
> iterations
> was determined at runtime?
> Regards
> ?Louis
>
> Louis Bertrand
> address@hidden
>




------------------------------

_______________________________________________
bug-cflow mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/bug-cflow


End of bug-cflow Digest, Vol 34, Issue 4
****************************************


reply via email to

[Prev in Thread] Current Thread [Next in Thread]