Hi, strace is very useful; it cuts below whatever the userspace language is and shows what's really happening.
I've a couple of suggestions. First, if an ioctl's third parameter looks like a memory address then optionally provide us with a few words of memory from there on. Whether that's a hexdump starting on a separate line, or a ioctl(..., 0xaddress [0x..., 0x...]), I don't mind. Perhaps the number of bytes/words could vary, like the length of strings with -s. I realise if may sometimes look like an address but not be one, or it may be an invalid address, especially by the time the Nth word is accessed, but that's for the reader to discern and it would still be useful in some cases where one's being passed strace's output and can start manually mapping the hex to the struct that particular ioctl expects. -- Cheers, Ralph. https://plus.google.com/+RalphCorderoy ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Strace-devel mailing list Strace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/strace-devel
