From: mathieu.desnoyers@efficios.com (Mathieu Desnoyers)
Subject: [lttng-dev] SIG33
Date: Tue, 16 Apr 2019 13:37:16 -0400 (EDT) [thread overview]
Message-ID: <483683232.2036.1555436236748.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <CAHryLm7o6X3pvu+=7m2b6TMFUMXNYhJOW8cid5v-FFTD948oHA@mail.gmail.com>
----- On Apr 16, 2019, at 11:26 AM, Joe Sutker <jomasu22 at gmail.com> wrote:
> Hello LTTng Devs,
> I am working on a project that uses LTTng, and it seems that LTTng is throwing a
> SIG33 signal (Real-time event 33), which Eclipse does not seem to appreciate.
> Would you be able to direct me to the place in lttng-tools that this signal is
> thrown?
Hi,
Based on the signal(7) man page, it appears that real-time signal 33 is used by the NPTL
threading library from glibc.
Indeed, lttng-ust creates 2 threads within the processes it's linked into, so
your application needs to appropriately interact with glibc NPTL in order to link
lttng-ust into it.
Can you provide more details on the nature of your application ? When you
say "which Eclipse does not seem to appreciate", what role is Eclipse having
in this scenario ? It is simply used to launch your application under a debugger
(e.g. gdb) ? If so, what debugger version is it, and on which architecture ?
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.lttng.org/pipermail/lttng-dev/attachments/20190416/4160fae7/attachment.html>
parent reply other threads:[~2019-04-16 17:37 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAHryLm7o6X3pvu+=7m2b6TMFUMXNYhJOW8cid5v-FFTD948oHA@mail.gmail.com>]
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=483683232.2036.1555436236748.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.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