This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC 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: default_weaktoshared timeouts

From: Jonathan Wakely <jwakely dot gcc at gmail dot com>
To: Jack Howarth <howarth at bromo dot med dot uc dot edu>
Cc: Paolo Carlini <paolo dot carlini at oracle dot com>, gcc at gcc dot gnu dot org, mikestump at comcast dot ne
Date: Wed, 21 Apr 2010 20:07:48 +0100
Subject: Re: default_weaktoshared timeouts
References: <20100402120928.GA10458@bromo.med.uc.edu> <4BB5DFC9.2040607@oracle.com> <20100402131237.GB10750@bromo.med.uc.edu> <s2x4348dea51004021010uc8e4c51amfe52efc8518b1cd4@mail.gmail.com> <20100402231656.GA13476@bromo.med.uc.edu>

On 3 April 2010 00:16, Jack Howarth wrote:
>
> Jonathan,
> ? ?The test program when compiled as i386 randomly hangs under both the 32-bit and 64-bit
> kernels on Darwin 10.3.0. I've emailed Mike Stump an Instruments trace file sampling the
> hung binary. Unfortunately, I don't know how to convert that to a human readable form
> to attach to a bug report. I'll open a bug report after Mike takes a look at the trace
> (just to make sure this shouldn't be a radar report instead).

Any word on this yet?
Does it hang if you run it under a debugger?  If so, you could just
stop it and print a stacktrace. Or does gdb's gstack utility work on
darwin?

Follow-Ups:
- Re: default_weaktoshared timeouts
  - From: Jack Howarth

References:
- default_weaktoshared timeouts
  - From: Jack Howarth
- Re: default_weaktoshared timeouts
  - From: Paolo Carlini
- Re: default_weaktoshared timeouts
  - From: Jack Howarth
- Re: default_weaktoshared timeouts
  - From: Jonathan Wakely
- Re: default_weaktoshared timeouts
  - From: Jack Howarth

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