public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin@cygwin.com
Cc: Joshuah Hurst <joshhurst@gmail.com>
Subject: Re: Debugging Cygwin apps with dtrace for windows?
Date: Thu, 31 Aug 2023 18:21:45 -0600	[thread overview]
Message-ID: <095fa450-cc6f-9b47-6124-0fc7acd5b1a2@Shaw.ca> (raw)
In-Reply-To: <CAEEMktORNMWdWYbUQFSs4ZoKyKHt6HtmH6+SvdR_v07gqFprTw@mail.gmail.com>

On 2023-08-31 16:49, Joshuah Hurst via Cygwin wrote:
> Has anyone tested if dtrace for windows
> https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/dtrace
> can be used to debug cygwin apps?

It does not appear to be usable as an application debugger, rather providing 
diagnostics about system call level behavioural anomalies, sampling system state 
with predefined interpreted AWK/C-like "D" scripts.

It appears to be a system call probe and event tracing and data collection tool, 
requiring a feature built in to recent Windows enabled, possibly built on Event 
Tracing for Windows, drivers, utilities, and matching OS symbols installed, 
offering command line initiated probe, event, executable, and user "D" script 
selection.

For cygwin executables, strace provides similar capabilities.

-- 
Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer     but when there is no more to cut
                                 -- Antoine de Saint-Exupéry

      reply	other threads:[~2023-09-01  0:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-31 22:49 Joshuah Hurst
2023-09-01  0:21 ` Brian Inglis [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=095fa450-cc6f-9b47-6124-0fc7acd5b1a2@Shaw.ca \
    --to=brian.inglis@shaw.ca \
    --cc=cygwin@cygwin.com \
    --cc=joshhurst@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).