Chewy509@[EMAIL PROTECTED]
wrote in part:
> What I have been trying to find is a decent profiling tool
> that can take a raw EXE (or a *.asm file), profile it,
> and let me know where the bottlenecks are so I can either,
> a, try to clean up the current algorithm being used, or b,
> find a better algorithm. eg, the number of times function
> x is called, and the duration in which that function takes.
You could start with `gprof` and similar profilers. They're
designed to work with C generated code with debugging symbols
left in the executable. Perhaps you can find a gnumeric mode
or provide the symbols.
-- Robert
|
