Bug 3761 - fstep is really, really slow
Summary: fstep is really, really slow
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
Depends on:
Blocks: 3364
  Show dependency treegraph
Reported: 2006-12-19 10:30 UTC by Mark Wielaard
Modified: 2007-08-28 10:18 UTC (History)
0 users

See Also:
Last reconfirmed:


Note You need to log in before you can comment on or make changes to this bug.
Description Mark Wielaard 2006-12-19 10:30:22 UTC
fstep is partially so slow because it accesses the Task memory for every
disassambly. Maybe that can be cached? Although instruction stepping is
just slow in general. An alternative could be combining stepping with
breakpoints set on "interesting functions". Or only stepping while in
the main program map, and not in any of the shared library maps?

Memory access is not only slow for fstep. Other programs (like fcore) also could
use faster access to the inferior memory.  One idea (at least for read access)
is mmapping the inferior address space (/proc/<pid>/mem), and/or performing
larger transfers and caching under the hood.
Comment 1 Mark Wielaard 2007-08-28 10:18:08 UTC
Fixed by the merger of AddressSpace and MemorySpace backends. Now normally reads
from /proc/pid/mem which make fstep just "slow", not terribly slow.