This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: 'recording' program execution.


On Fri, Oct 31, 2008 at 10:18 AM, wuxi <wu.andrew.xi@gmail.com> wrote:
> muenchen@physik.uni-wuppertal.de wrote:
>>
>> have a look at the flag -finstrument-functions for gcc.
>
> as far as I know, this could only record at function entry and return ?
>
> but sometimes recording all the "trace" of how program behaves is useful for
> debugging purpose.
>
> further, using a binary instrumentation tool like PIN could only record the
> low level instruction trace....

I would suggest to do the instrumentation in the frontends as there
you still know
the original statement boundaries.  Note that the original program text may be
not readily available there, so you might need to hack libcpp as well.

Richard.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]