public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* strace 2.6.0 microsecond timing is not output
@ 2017-01-07 17:33 Keith Christian
  2017-01-08  0:46 ` Mark Geisert
  0 siblings, 1 reply; 2+ messages in thread
From: Keith Christian @ 2017-01-07 17:33 UTC (permalink / raw)
  To: cygwin

While testing the output of "windres" in Steven Penny's post earlier,
I used strace.

I don't see the microsecond timing output in the current strace
version 2.6.0.  (Output has no special relation to "windres.")


foo$ strace -o windres.strace_${RANDOM} -t -u windres


foo$ tail windres.strace_22198

00:00:05 [main] windres 56768 fhandler_console::free_console: freed
console, res 1
00:00:05 [main] windres 56768 fhandler_pty_common::close: pty4
<0xE4,0xEC> closing
00:00:05 [main] windres 56768 dtable::delete_archetype: deleting
element 0 for /dev/pty4(136/4)
00:00:05 [main] windres 56768 getpid: 56768 = getpid()
00:00:05 [main] windres 56768 proc_terminate: nprocs 0
00:00:05 [main] windres 56768 proc_terminate: leaving
00:00:05 [main] windres 56768 pinfo::exit: Calling ExitProcess n
0x100, exitcode 0x1
--- Process 56768 thread 55472 exited with status 0x1
--- Process 56768 thread 57248 exited with status 0x1
--- Process 56768 exited with status 0x1


Am I missing something here?

Keith

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2017-01-08  0:46 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-01-07 17:33 strace 2.6.0 microsecond timing is not output Keith Christian
2017-01-08  0:46 ` Mark Geisert

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).