From: pierre <pierre@silentlife.com>
To: musl@lists.openwall.com, Rich Felker <dalias@aerifal.cx>
Subject: Re: dladdr()
Date: Tue, 22 Jan 2013 07:27:46 +0100 [thread overview]
Message-ID: <1358836066.2172.45.camel@6-core> (raw)
In-Reply-To: <20130121183523.GP20323@brightrain.aerifal.cx>
Rich,
> I don't see how any of these could crash without
> memory already having been corrupted.
That's what I wrote previously: my code populates
backtraces which could have been damaged by stack
smashing.
Backtraces are used to identify the cause of a crash,
which, by definition, may not be clean.
The information I wanted you guys to have is that,
for the same application code, both GLIBC and musl
compiled in DEBUG mode do not crash (while musl in
release mode crashes).
> Do you have a test case I could run,
In my previous email (the one you are answering)
I wrote:
"I did not have time to isolate the problem in a
reproducible code snippet but I will let you
know when I have done that."
> have you tried building libc with -g and examining
> the crash in gdb to see where it happens?
In my previous email (the one you are answering)
I wrote:
"for my main application (which populates backtraces
with dladdr), musl dladdr() works in DEBUG mode and
crashes in RELEASE mode."
The musl "DEBUG mode" tested here used -g2 and it did
not crash.
I am not trying to argue with you - there's no point
at doing that - I was merely providing the information
I had available when you asked "does it work for you?".
Pierre
next prev parent reply other threads:[~2013-01-22 6:27 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 17:17 malloc(0) behaviour Igmar Palsenberg
2013-01-14 18:05 ` Rich Felker
2013-01-14 22:22 ` Strake
2013-01-14 23:05 ` Rich Felker
2013-01-15 8:32 ` Igmar Palsenberg
2013-01-15 12:53 ` Rob Landley
2013-01-15 22:18 ` Igmar Palsenberg
2013-01-15 8:31 ` Igmar Palsenberg
2013-01-15 11:06 ` Szabolcs Nagy
2013-01-15 12:33 ` Igmar Palsenberg
2013-01-15 13:48 ` Rich Felker
2013-01-15 22:28 ` Igmar Palsenberg
2013-01-15 23:22 ` Rob
2013-01-16 7:46 ` Igmar Palsenberg
2013-01-15 13:46 ` Rich Felker
2013-01-15 12:52 ` Rob Landley
2013-01-14 23:37 ` Rob Landley
2013-01-15 0:24 ` Rich Felker
2013-01-15 12:17 ` Rob Landley
2013-01-15 9:01 ` Igmar Palsenberg
2013-01-15 12:58 ` Rob Landley
2013-01-15 14:54 ` dladdr() pierre
2013-01-15 18:48 ` dladdr() Rich Felker
2013-01-16 11:00 ` dladdr() pierre
2013-01-16 12:51 ` dladdr() Szabolcs Nagy
2013-01-16 14:24 ` dladdr() musl
2013-01-16 15:20 ` dladdr() pierre
2013-01-16 16:49 ` dladdr() Rich Felker
2013-01-16 17:42 ` dladdr() musl
2013-01-21 2:03 ` dladdr() Rich Felker
2013-01-21 6:58 ` dladdr() pierre
2013-01-21 18:35 ` dladdr() Rich Felker
2013-01-22 6:27 ` pierre [this message]
2013-01-22 13:07 ` dladdr() Szabolcs Nagy
2013-01-22 13:40 ` dladdr() pierre
2013-01-22 13:51 ` dladdr() Rich Felker
2013-01-22 14:59 ` dladdr() pierre
2013-01-22 16:11 ` dladdr() Szabolcs Nagy
2013-01-22 23:43 ` dladdr() Rich Felker
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=1358836066.2172.45.camel@6-core \
--to=pierre@silentlife.com \
--cc=dalias@aerifal.cx \
--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).