From: Jean-Marc Pigeon <jmp@safe.ca>
To: musl@lists.openwall.com
Subject: Re: Execinfo.h, backtrace is needed.
Date: Fri, 10 Apr 2015 10:30:23 -0400 [thread overview]
Message-ID: <5527DE7F.4030802@safe.ca> (raw)
In-Reply-To: <alpine.LNX.2.11.1504092038030.338@monopod.intra.ispras.ru>
[-- Attachment #1: Type: text/plain, Size: 2090 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
On 04/09/2015 01:57 PM, Alexander Monakov wrote:
[...]
> Please note: libbacktrace may be overkill if you don't need DWARF
> parsing at runtime. For example, if you can perform symbol
> resolution separately as post-processing, and capturing only stack
> frame addresses at runtime suffices, libunwind may be the tool for
> the job. Also, libunwind provides backtrace() as a weak alias to
> its own unw_backtrace(), so in simple cases it's a drop-in
> replacement.
>
> Hope that helps. Alexander
Many thanks for your help,
installed and using now libunwind, it is exactly what was
needed, just replacing backtrace by unw_backtrace.
Still using addr2line to display the exact "memory leak
origine".
- --
A bientôt
===========================================================
Jean-Marc Pigeon E-Mail: jmp@safe.ca
SAFE Inc. Phone: (514) 493-4280
Clement, 'a kiss solution' to get rid of SPAM (at last)
Clement' Home base <"http://www.clement.safe.ca">
===========================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJVJ95/AAoJEAtgwJ4bBQU5XXwP/2rJrGvgiohS7DVe9ivKDOYK
Q/v0txAIq+RRdwxV2rPX3nFvtHWNvkMb/HQ7wdVZUkVSFzL09+q/E+HxEK5lcMP3
SHvIcy7CiECRMtnui2CHb84COKGH27T6M5L5iPs7MqjFNcbMEu0vITl6QeY6l5IQ
5qCotHYGfPBTxJz8ZYPfcTdwko6emSunKdmgzQMkFi6VKyv2OriJ5v0nm+2qajR2
G7rO97yS3eq0gdw+e7M3o5nGnqJWaz1NMCA2V259AWfElvCYFFIyQAkMRUjGC6AX
2Z9fMxg7JtVI1evxi9LUr/wQNQKJwr08GygWvdErcXgrJXJ0R/WOIJ46JSjAszUq
XDsOJIEMDPurSi5cxV5GyVx7RtncRgM2AW+Pe4jFQLg0plXiMNCpHv6SVon268e5
5dzDwvfAVnP80Ed2j/L3cOquO16D7SxwnlIN8lKD6swTbtl/UnMmyOjU8iAwzXTX
AgpXzYdGpE9nnV1pGAdGTeqD2TURAtA1Qv3GSTi0O06aAfuUIJOyxs/pNIlVSQip
JuyGBdanDsJ4WflFCzmbosMRTo50/qlXMVCDm94bgjtPKAha+y9vOipDFDcTGzc6
HL+Z+AjzIjdE02ea0ZVL2wBLOM+cdfqSqIGx47Y0V4WZKFfYnJpUji1w8/bt82q5
YEQB5mEdkineURcW0q5g
=GYIL
-----END PGP SIGNATURE-----
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4242 bytes --]
next prev parent reply other threads:[~2015-04-10 14:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 15:33 musl perf, 20% slower than native build? John Mudd
2015-04-08 15:58 ` Alexander Monakov
2015-04-08 16:05 ` Szabolcs Nagy
2015-04-08 19:10 ` John Mudd
2015-04-08 19:28 ` Daniel Cegiełka
2015-04-08 20:59 ` Paul Schutte
2015-04-09 6:50 ` Daniel Cegiełka
2015-04-09 17:28 ` Execinfo.h, backtrace is needed Jean-Marc Pigeon
2015-04-09 17:34 ` Rich Felker
2015-04-09 17:57 ` Alexander Monakov
2015-04-10 14:30 ` Jean-Marc Pigeon [this message]
2015-04-08 19:33 ` musl perf, 20% slower than native build? Alexander Monakov
2015-04-08 20:16 ` John Mudd
2015-04-08 20:24 ` John Mudd
2015-04-08 21:48 ` John Mudd
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=5527DE7F.4030802@safe.ca \
--to=jmp@safe.ca \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).