From: "H.J. Lu" <hjl.tools@gmail.com>
To: "Craig Silverstein" <csilvers@google.com>
Cc: binutils@sourceware.org, dj@redhat.com, drow@false.org,
gdb@sourceware.org, hp@bitrange.com
Subject: Re: inflateInit?
Date: Sun, 13 Jul 2008 23:42:00 -0000 [thread overview]
Message-ID: <6dc9ffc80807131641n687a6c8gdffff95aa109751f@mail.gmail.com> (raw)
In-Reply-To: <20080713225758.3B98D3F305E@localhost>
On Sun, Jul 13, 2008 at 3:57 PM, Craig Silverstein <csilvers@google.com> wrote:
> } ./addr2line -e ./addr2line `nm -n --defined-only ./addr2line |head
> } -1 | awk '{print $1}'`
>
> Yes, it works on all the ones I've tested on. I'm still trying to
> reproduce the problem you reported.
>
> craig
>
Some glibc, like the one in Fedora 9, will check invalid pointers passed to
free by default. If you use Linux, you can try
[hjl@gnu-26 binutils]$ MALLOC_CHECK_=1 ./addr2line -e ./addr2line `nm
-n --defined-only ./addr2line |head -1 | awk '{print $1}'`
malloc: using debugging hooks
??:0
*** glibc detected *** free(): invalid pointer: 0x0000002a95734d53 ***
[hjl@gnu-26 binutils]$
--
H.J.
next prev parent reply other threads:[~2008-07-13 23:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 15:18 inflateInit? DJ Delorie
2008-07-10 16:14 ` inflateInit? Daniel Jacobowitz
2008-07-10 16:53 ` inflateInit? Craig Silverstein
2008-07-10 17:24 ` inflateInit? DJ Delorie
2008-07-10 18:52 ` inflateInit? Craig Silverstein
2008-07-10 19:24 ` inflateInit? DJ Delorie
2008-07-10 20:12 ` inflateInit? Daniel Jacobowitz
2008-07-10 20:36 ` inflateInit? Craig Silverstein
2008-07-10 22:11 ` inflateInit? Hans-Peter Nilsson
2008-07-11 0:56 ` inflateInit? Craig Silverstein
2008-07-12 18:28 ` inflateInit? H.J. Lu
2008-07-12 19:37 ` inflateInit? Craig Silverstein
2008-07-13 15:58 ` inflateInit? H.J. Lu
2008-07-13 19:34 ` inflateInit? Craig Silverstein
2008-07-13 19:47 ` inflateInit? H.J. Lu
2008-07-13 22:58 ` inflateInit? Craig Silverstein
2008-07-13 23:42 ` H.J. Lu [this message]
2008-07-10 20:40 ` inflateInit? Craig Silverstein
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=6dc9ffc80807131641n687a6c8gdffff95aa109751f@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=binutils@sourceware.org \
--cc=csilvers@google.com \
--cc=dj@redhat.com \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=hp@bitrange.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox