All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stotland, Inga <inga.stotland@intel.com>
To: ell@lists.01.org
Subject: Re: Debug logging with ell
Date: Tue, 24 Apr 2018 21:54:25 +0000	[thread overview]
Message-ID: <1524606863.3034.31.camel@intel.com> (raw)
In-Reply-To: <CAPyD+=AE=7WiOqCumVyvNCtPpWFFMiZKk6eeg0bLeOVcqHETxw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1239 bytes --]

Hi Ossama, Denis,
   A. 
On Tue, 2018-04-24 at 14:35 -0700, Othman, Ossama wrote:
> Hi Denis,
> 
> On Tue, Apr 24, 2018 at 1:30 PM, Denis Kenzior <denkenz@gmail.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.
> > > 
> > 
> > I suspect you're the first to try this, so doesn't surprise me that
> > it
> > doesn't work.  I imagine the current setup fails because the shared
> > library
> > has its own section and the executable has its own.
> > 
> > Probably can be solved with some macro magic, but will require a
> > bit of
> > surgery inside ell...
> 
> This used to work for me, but prior to today the last time I tried
> enabling debug logging code was probably a couple of months ago.
> 

Most likely to do with memory sections. One additional piece of info in
case it's helpful:
The section denoted by __start___debug[] and __stop___debug[] appears
to be shorter by size of one struct l_debug_desc when linking with
-lell (compared when compiled with internal lib). 

Inga

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3266 bytes --]

  reply	other threads:[~2018-04-24 21:54 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
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 [this message]
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=1524606863.3034.31.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.