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("*");

Hi all, 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.

Hi Denis, On Tue, Apr 24, 2018 at 1:30 PM, Denis Kenzior <denkenz(a)gmail.com&gt; 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.

On 04/24/2018 11:33 AM, Stotland, Inga 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. So this should work now. I've pushed a couple of fixes upstream.