From: Stotland, Inga <inga.stotland@intel.com>
To: ell@lists.01.org
Subject: Re: Debug logging with ell
Date: Tue, 24 Apr 2018 19:56:59 +0000 [thread overview]
Message-ID: <1524599816.3034.23.camel@intel.com> (raw)
In-Reply-To: <CAPyD+=BDGLT8WYTZEthm9ROfRSY6fbBJyZMLCuRoXPFcLp0yCQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 819 bytes --]
Hi Ossama,
On Tue, 2018-04-24 at 10:35 -0700, Othman, Ossama wrote:
> Hi Inga,
>
> On Tue, Apr 24, 2018 at 9:33 AM, Stotland, Inga <inga.stotland@intel.
> com> wrote:
> >
> > Quick question: can I use l_debug() when I am dynamically linking
> > with
> > installed ell library (i.e., the one created with make install and
> > linked as -lell)?
> > Calling l_debug() generates no output, l_info() works just fine.
> >
> > When I link with libell-private, l_debug works as expected.
> > Something
> > to do with debug mem sections?
> >
> > I would rather not write my own logging if l_debug() is
> > available.
>
> Try enabling debug logging at run-time, e.g.: l_debug_enable("*");
I do have the following statements in my code:
l_log_set_stderr();
l_debug_enable("*");
Thanks,
Inga
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3266 bytes --]
next prev parent reply other threads:[~2018-04-24 19:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 16:33 Debug logging with ell Stotland, Inga
2018-04-24 17:35 ` Othman, Ossama
2018-04-24 19:56 ` Stotland, Inga [this message]
2018-04-24 21:33 ` Othman, Ossama
2018-04-24 20:30 ` Denis Kenzior
2018-04-24 21:35 ` Othman, Ossama
2018-04-24 21:54 ` Stotland, Inga
2018-04-25 20:23 ` Denis Kenzior
2018-04-25 20:28 ` Othman, Ossama
2018-04-26 1:23 ` Stotland, Inga
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=1524599816.3034.23.camel@intel.com \
--to=inga.stotland@intel.com \
--cc=ell@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.