public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Martin Cermak <mcermak@redhat.com>
To: Ryan Goldberg <rgoldber@redhat.com>
Cc: systemtap@sourceware.org
Subject: Re: Introducing the Systemtap Language-server
Date: Tue, 14 Feb 2023 08:42:13 +0100	[thread overview]
Message-ID: <20230214074213.bjzsl7unhul356gf@lida.tpb.lab.eng.brq.redhat.com> (raw)
In-Reply-To: <20230206094752.h4ltkc7hnfyhta57@lida.tpb.lab.eng.brq.redhat.com>

On  Mon  2023-02-06  10:47 , Martin Cermak wrote:
> On  Fri  2023-02-03  15:06 , Ryan Goldberg via Systemtap wrote:
> > Hi all,
> > 
> > A new language-server [0] mode has recently been added to systemtap. The
> > language-server, which runs as a child of an lsp-client [1], serves up
> > code-completion suggestions.
> > 
> > The language-server-protocol uses jsonrpc [2] and we developed our own C++
> > SDK which both implements jsonrpc and allows for the creation of
> > language-servers.
> > 
> > We use systemtap's pass 1 machinery in order to lex and parse
> > code-completion requests and then use the termination state to determine
> > the completion results as well as some metadata (such as the result type).
> > Further deriving these allows us to provide additional context-specific
> > completion results such as context variables within applicable probe
> > statement blocks or string completions within probe components. The server
> > also provides completions for globals, functions and macros from both
> > within the script and from the tapsets.
> > 
> > The language server can be run with "stap --language-server" and should be
> > started by a language-server client as the data is currently transferred
> > via stdin/stdout. We have currently been testing with vim, emacs, vscode,
> > jupyter and eclipse. Take a look at language-server/README.md for client
> > specific usage instructions.
> > 
> > For more information I'll be releasing a blog post later this year
> > describing the jupyter-notebook use case of the language-server. If you
> > have any feedback, I'd be happy to hear it.
> 
> Hi Ryan, the source doesn't compile on RHEL.  RHEL9 currently only
> has json-c-devel-0.14 which doesn't provide json_object_new_array_ext().
> It only las json_object_new_array()  This seems to be the only
> compilation problem on RHEL9.
> 
> However, systemtap is also supposed to work with RHEL8, where I
> seem to see more compile time issues.  Please, check.  I'm happy
> to provide a test box for you if interested.

... thanks, for the fixes;  Works great for me now!

Martin


      reply	other threads:[~2023-02-14  7:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-03 20:06 Ryan Goldberg
2023-02-06  9:47 ` Martin Cermak
2023-02-14  7:42   ` Martin Cermak [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=20230214074213.bjzsl7unhul356gf@lida.tpb.lab.eng.brq.redhat.com \
    --to=mcermak@redhat.com \
    --cc=rgoldber@redhat.com \
    --cc=systemtap@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).