This is the mail archive of the cygwin mailing list for the Cygwin 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: How to detect a cygwin thread?

On Mon, 11 May 2009, Piotr Wyderski wrote:

> Christopher Faylor wrote:
> > Yes, that's the signal thread but I don't know why stopping it would
> > cause any special problems since, if the entire program is stopped, it
> > isn't going to be processing signals.
> I don't know the reason, just report the program's
> behaviour. But to provide you more context: this
> code is a critical error handler. All it has to do is:
> 1. immediately stop the world in a nice way,
> as this thread is all about. When "sig" is suspended,
> no more points follow.
> 2. dump detailed stack traces + module list +
> the emergency stop reason description to
> the set of log files;

My WAG is:

A handshake with the signal thread is required for many Cygwin system
calls to proceede.

> The need for parsing DWARF sections by the
> user himself is a difficult and painstaking challenge.

Have you considered libdwarf?  I have a build that works using a custom
minimal libelf stub library.  I don't use if for back traces at the
moment, but it can read symbolic program variable information.

Brian Ford
Staff Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
the best safety device in any aircraft is a well-trained crew...

Unsubscribe info:
Problem reports:

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