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: Paul Eggert <eggert at cs dot ucla dot edu>
Cc: "Carlos O'Donell" <carlos at redhat dot com>, libc-alpha at sourceware dot org
Date: Fri, 27 Feb 2015 13:52:37 +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> <54EF9B9C dot 1080305 at redhat dot com> <20150227071658 dot GZ23807 at spoyarek dot pnq dot redhat dot com> <54F01DDD dot 7090306 at cs dot ucla dot edu>

On Thu, Feb 26, 2015 at 11:33:49PM -0800, Paul Eggert wrote:
> Siddhesh Poyarekar wrote:
> >A new function backtrace_init() could help break this deadlock.
> 
> Or we could document the current behavior, which is that backtrace (0, 0)
> initializes the backtrace module and avoids the problem.  This is pretty
> much what bleeding-edge Emacs does now.  (Unfortunately this does not work
> on sparc or microblaze but those would presumably be considered bugs.)

Oh great, that is even better since it doesn't need an ABI event.

Siddhesh

Attachment: pgplS1LImub5E.pgp
Description: PGP signature

References:
- [PATCH] Avoid deadlock in malloc on backtrace
  - From: Siddhesh Poyarekar
- Re: [PATCH] Avoid deadlock in malloc on backtrace
  - From: Carlos O'Donell
- Re: [PATCH] Avoid deadlock in malloc on backtrace
  - From: Siddhesh Poyarekar
- Re: [PATCH] Avoid deadlock in malloc on backtrace
  - From: Paul Eggert

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