public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
* [Linux-ia64] strace update
@ 2001-10-10  0:17 David Mosberger
  0 siblings, 0 replies; only message in thread
From: David Mosberger @ 2001-10-10  0:17 UTC (permalink / raw)
  To: linux-ia64

Just FYI: Wichert just got around to update the CVS tree with my
latest ia64 updates (thanks, Wichert!).  These updates bring the main
CVS branch in sync with the changes from the ia64 branch.  The latter
should no longer be needed and I'd recommend switching away from it
(after sufficient testing, of course...).

I should say that the old ia64 branch handled the argument printing of
*some* of the ia32 syscalls a bit better, but OTOH, it failed
completely on others (often failing with spurious errors or printing
garbage for some syscall args).  In the main branch, ia32 syscalls
with arguments that are have a different format than the corresponding
ia64 syscall are handled simply by printing the arguments as hex
numbers.  This isn't always very readable, but if it's a real issue,
we can add proper ia32 argument printing gradually over time.  The
goal for now was to be on the safe side.  If you see any "umoven"
errors when stracing x86 binaries, there was an omission somewhere and
I'd like to hear about it.  In my opinion, the hex printing is usually
good enough because with recent kernels, you always have the option of
running the ia32 version of strace.

The other reason why you might want to try out the new strace is that
it finally supports strace -f across thread creation (not just across
fork()).

Enjoy,

	--david

PS: And no, this doesn't mean that I want to be the ia64 strace
    maintainer... ;-)


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2001-10-10  0:17 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-10-10  0:17 [Linux-ia64] strace update David Mosberger

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox