This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] Avoid deadlock in malloc on backtrace

From: Siddhesh Poyarekar <siddhesh at redhat dot com>
To: Florian Weimer <fweimer at redhat dot com>
Cc: libc-alpha at sourceware dot org, carlos at redhat dot com
Date: Tue, 24 Feb 2015 17:33:40 +0530
Subject: Re: [PATCH] Avoid deadlock in malloc on backtrace
Authentication-results: sourceware.org; auth=none
References: <20150224100249 dot GA31871 at spoyarek dot pnq dot redhat dot com> <54EC52E6 dot 5010905 at redhat dot com> <20150224115158 dot GH23807 at spoyarek dot pnq dot redhat dot com> <54EC66CF dot 30800 at redhat dot com>

On Tue, Feb 24, 2015 at 12:55:59PM +0100, Florian Weimer wrote:
> I think we should really consider removal.  Most distributions will
> have core dump catchers once they start using a glibc version derived
> from master.

I don't need a lot of convincing for this, but I guess we need more
consensus.  Does anybody think that removing the backtrace and maps is
a bad idea?

> I get that, I was suggesting a way to future-proof the test case
> against compiler changes.

Ahh OK, I get it now.

Thanks,
Siddhesh

Attachment: pgppWeiWeUp1F.pgp
Description: PGP signature

Follow-Ups:
- Re: [PATCH] Avoid deadlock in malloc on backtrace
  - From: Florian Weimer

References:
- [PATCH] Avoid deadlock in malloc on backtrace
  - From: Siddhesh Poyarekar
- Re: [PATCH] Avoid deadlock in malloc on backtrace
  - From: Florian Weimer
- Re: [PATCH] Avoid deadlock in malloc on backtrace
  - From: Siddhesh Poyarekar
- Re: [PATCH] Avoid deadlock in malloc on backtrace
  - From: Florian Weimer

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]