From: Eli Zaretskii <eliz@gnu.org>
To: Eduard Sargsyan <eduard.sargsyan@intel.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/1] doc: update link to Oracle DTrace project
Date: Wed, 20 Dec 2023 13:58:09 +0200 [thread overview]
Message-ID: <83v88tgk6m.fsf@gnu.org> (raw)
In-Reply-To: <20231219144500.19442-2-eduard.sargsyan@intel.com> (message from Eduard Sargsyan on Tue, 19 Dec 2023 14:45:00 +0000)
> From: Eduard Sargsyan <eduard.sargsyan@intel.com>
> Date: Tue, 19 Dec 2023 14:45:00 +0000
>
> ---
> gdb/doc/gdb.texinfo | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
> index 7a5d357b99b..d69c733c723 100644
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -6141,7 +6141,7 @@ from assembly, C and C@t{++} languages@footnote{See
> @uref{http://sourceware.org/systemtap/wiki/UserSpaceProbeImplementation}
> for a good reference on how the @acronym{SDT} probes are implemented.}.
>
> -@item @code{DTrace} (@uref{http://oss.oracle.com/projects/DTrace})
> +@item @code{DTrace} (@uref{https://docs.oracle.com/en/operating-systems/oracle-linux/dtrace-guide/})
> @acronym{USDT} probes. @code{DTrace} probes are usable from C and
> C@t{++} languages.
> @end itemize
Thanks, but I wonder whether there are sites that document this but
are not related to specific commercial entities.
next prev parent reply other threads:[~2023-12-20 11:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 14:44 [PATCH 0/1] The link to DTrace needs to be updated Eduard Sargsyan
2023-12-19 14:45 ` [PATCH 1/1] doc: update link to Oracle DTrace project Eduard Sargsyan
2023-12-20 11:58 ` Eli Zaretskii [this message]
2023-12-20 12:01 ` Sargsyan, Eduard
2023-12-20 13:24 ` Eli Zaretskii
2023-12-20 13:29 ` Sargsyan, Eduard
2024-01-18 11:14 ` Sargsyan, Eduard
2024-01-18 12:23 ` Eli Zaretskii
2024-01-19 16:51 ` Elena Zannoni
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=83v88tgk6m.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eduard.sargsyan@intel.com \
--cc=gdb-patches@sourceware.org \
/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).