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: Paul Eggert <eggert at cs dot ucla dot edu>
To: Siddhesh Poyarekar <siddhesh at redhat dot com>, Carlos O'Donell <carlos at redhat dot com>
Cc: libc-alpha at sourceware dot org
Date: Thu, 26 Feb 2015 23:33:49 -0800
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>

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 muchwhat bleeding-edge Emacs does now. (Unfortunately this does not work on sparcor microblaze but those would presumably be considered bugs.)

Follow-Ups:
- Re: [PATCH] Avoid deadlock in malloc on backtrace
  - From: Siddhesh Poyarekar

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

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