For logging, perhaps a record button that would record up to some fixed
cache size and then auto-pause the program. To continue, the cache would
need to be cleared.
Data mining the trace is a great idea, a simple use case I was considering
was to detect data stride / structure size to better layou
- Original Message -
>
> Slow down / pause is something that's planned. Rewind is difficult
> since this would require actually logging the trace data (currently
> it's transient), which would take up a huge amount of space - though
> this may be useful for short-lived programs.
Hi
Is it
On Apr 11, 2013, at 9:00 AM CDT, Andrew Clinton wrote:
> Slow down / pause is something that's planned. Rewind is difficult since
> this would require actually logging the trace data (currently it's
> transient), which would take up a huge amount of space - though this may be
> useful for sho
Slow down / pause is something that's planned. Rewind is difficult since
this would require actually logging the trace data (currently it's
transient), which would take up a huge amount of space - though this may be
useful for short-lived programs.
On Thu, Apr 11, 2013 at 5:49 AM, Thomas Rast
Andrew Clinton writes:
> I've been working on a new valgrind tool and graphical front end for
> visualizing memory traces and graphically representing program address
> space. It's becoming fairly complete - so I thought I'd post here to see
> if any valgrind users/developers are interested in t
On 04/09/2013 09:42 PM, Andrew Clinton wrote:
> I've been working on a new valgrind tool and graphical front end for
> visualizing memory traces and graphically representing program address space.
Welcome to the club.
John F Reiser, Static Initializers: Reducing the Value-Added Tax on Programs,
