[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: tpool cleanup?
- To: lukeh@padl.com
- Subject: Re: tpool cleanup?
- From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
- Date: Tue, 2 May 2006 17:11:07 +0200
- Cc: openldap-devel@OpenLDAP.org
- In-reply-to: <200604300232.k3U2WCCw010078@au.padl.com>
- References: <1143839562.4496.21.camel@ando> <445191BD.3090609@symas.com> <1146322584.3792.17.camel@ando> <4453CD7E.2030707@symas.com> <4453D285.7040306@symas.com> <hbf.20060430mdu@bombur.uio.no> <200604300232.k3U2WCCw010078@au.padl.com>
Luke Howard writes:
>> Yes, memory debuggers like Valgrind can show a stack trace of where the
>> resource was created. thr_debug can't do that, so the output is more
>> informative when it provokes Valgrind instead.
>
> On Linux you can call backtrace_symbols_fd() to get a backtrace from
> within your application.
Thanks. I'll check that out someday.
--
Hallvard