public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "arun dot sharma at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/24724] _Unwind_Backtrace() calls malloc
Date: Tue, 08 Nov 2005 01:09:00 -0000	[thread overview]
Message-ID: <20051108010906.2316.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24724-11484@http.gcc.gnu.org/bugzilla/>



------- Comment #8 from arun dot sharma at google dot com  2005-11-08 01:09 -------
(In reply to comment #6)
> Hmm, You could try libunwind instead, it should work on x86_64:
> http://www.hpl.hp.com/research/linux/libunwind/
> 
> They show you how to use libunwind to generate a normal backtrace:
> http://www.hpl.hp.com/research/linux/libunwind/man/libunwind(3).php
> 
> Though I doubt that none of these will remove the use of malloc though.
> 

libunwind doesn't pass unit tests on amd64. davidm thinks that the problems are
outside of libunwind. I think he has a couple of bugs open against gcc/glibc.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24724


  parent reply	other threads:[~2005-11-08  1:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-07 23:24 [Bug c/24724] New: " arun dot sharma at google dot com
2005-11-08  0:23 ` [Bug other/24724] " pinskia at gcc dot gnu dot org
2005-11-08  0:48 ` arun dot sharma at google dot com
2005-11-08  0:51 ` pinskia at gcc dot gnu dot org
2005-11-08  0:53 ` pinskia at gcc dot gnu dot org
2005-11-08  0:55 ` arun dot sharma at google dot com
2005-11-08  1:02 ` pinskia at gcc dot gnu dot org
2005-11-08  1:07 ` arun dot sharma at google dot com
2005-11-08  1:09 ` arun dot sharma at google dot com [this message]
2005-11-08  1:10 ` pinskia at gcc dot gnu dot org
2005-11-08  1:13 ` pinskia at gcc dot gnu dot org
2005-11-08  1:23 ` pinskia at gcc dot gnu dot org
2005-11-08  1:30 ` arun dot sharma at google dot com
2010-08-04 23:08 ` rth at gcc dot gnu dot org
     [not found] <bug-24724-4@http.gcc.gnu.org/bugzilla/>
2012-09-13 13:44 ` hjl.tools at gmail dot com
2012-09-13 14:06 ` ian at airs dot com
2012-09-13 14:20 ` hjl.tools at gmail dot com

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=20051108010906.2316.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).