RE: cancelling

RE: cancelling

[Bossom, John]

Now, originally I implemented the pthread_cancel mechanism
with Microsoft's SEH (Structured Exception Handling)
and internally the BAD DEED is being thrown using this
mechanism and being caught by the thread start routine.

You should check to see if someone changed the thread
start routine to use the C++ exception mechanism.

The drawback of SEH is that it doesn't work well
with C++ as it bypasses the C++ stack unwinding
(i.e. calling destructors).

This could be handled by using a hook function that
maps SEH into C++ exceptions and using C++ exception
handling in your mainline for your thread. You'll
have to do some reading on providing the hook in
the Microsoft documentation. (I haven't done this
but it seems like a good theory anyway ;^)

John.

-----Original Message-----
From: Thomas Sailer [ mailto:sailer@ife.ee.ethz.ch ]
Sent: Wednesday, July 12, 2000 7:21 AM
To: Bossom, John
Cc: pthreads-win32@sourceware.cygnus.com
Subject: Re: cancelling


"Bossom, John" wrote:

> Check to see if the code base for pthread is wrapping
> an exception handler around your thread mainline
> (the original code had an internal routine called "threadStart"
> which used Microsoft's Structured Exception Handling for catching all
> exceptions raised in your thread.)

The thread I'm trying to cancel was created with pthread_create,
and internally the thread routine is started through
_pthread_threadStart, which should be fine.

The thread that tries to cancel is the initial thread, i.e.
the one that called _main.

> Now, your thread is recognizing the cancel (the exception
> hex value is human readable: BAD DEED) and should have

I thought that the constant wasn't chosen arbitrarily :))

Tom

Re: cancelling

[Lorin Hochstein]

See the documentation on the "_set_se_translator" function for translating
to SEH to C++ exceptions.

Lorin Hochstein

----- Original Message -----
From: "Bossom, John" <John.Bossom@Cognos.COM>
To: "'Thomas Sailer'" <sailer@ife.ee.ethz.ch>; "Bossom, John"
<John.Bossom@Cognos.COM>
Cc: <pthreads-win32@sourceware.cygnus.com>
Sent: Wednesday, July 12, 2000 10:33 AM
Subject: RE: cancelling


> Now, originally I implemented the pthread_cancel mechanism
> with Microsoft's SEH (Structured Exception Handling)
> and internally the BAD DEED is being thrown using this
> mechanism and being caught by the thread start routine.
>
> You should check to see if someone changed the thread
> start routine to use the C++ exception mechanism.
>
> The drawback of SEH is that it doesn't work well
> with C++ as it bypasses the C++ stack unwinding
> (i.e. calling destructors).
>
> This could be handled by using a hook function that
> maps SEH into C++ exceptions and using C++ exception
> handling in your mainline for your thread. You'll
> have to do some reading on providing the hook in
> the Microsoft documentation. (I haven't done this
> but it seems like a good theory anyway ;^)
>
> John.
>
> -----Original Message-----
> From: Thomas Sailer [ mailto:sailer@ife.ee.ethz.ch ]
> Sent: Wednesday, July 12, 2000 7:21 AM
> To: Bossom, John
> Cc: pthreads-win32@sourceware.cygnus.com
> Subject: Re: cancelling
>
>
> "Bossom, John" wrote:
>
> > Check to see if the code base for pthread is wrapping
> > an exception handler around your thread mainline
> > (the original code had an internal routine called "threadStart"
> > which used Microsoft's Structured Exception Handling for catching all
> > exceptions raised in your thread.)
>
> The thread I'm trying to cancel was created with pthread_create,
> and internally the thread routine is started through
> _pthread_threadStart, which should be fine.
>
> The thread that tries to cancel is the initial thread, i.e.
> the one that called _main.
>
> > Now, your thread is recognizing the cancel (the exception
> > hex value is human readable: BAD DEED) and should have
>
> I thought that the constant wasn't chosen arbitrarily :))
>
> Tom

Re: cancelling

[Thomas Sailer]

"Bossom, John" wrote:
> 
> Now, originally I implemented the pthread_cancel mechanism
> with Microsoft's SEH (Structured Exception Handling)
> and internally the BAD DEED is being thrown using this
> mechanism and being caught by the thread start routine.
> 
> You should check to see if someone changed the thread
> start routine to use the C++ exception mechanism.

The code currently seems to support three mechanisms:

if _MSC_VER is defined, it seems to be using SEH.

otherwise, if __cplusplus is defined, it seems to
be using C++ EH.

otherwise, it just starts the thread without any
exception handling.

Now the question is how the precompiled
DLL on the net was compiled.

Tom

Re: cancelling

[Ross Johnson]

Thomas Sailer wrote:
> 
> The code currently seems to support three mechanisms:
> 
> if _MSC_VER is defined, it seems to be using SEH.
> 
> otherwise, if __cplusplus is defined, it seems to
> be using C++ EH.
> 
> otherwise, it just starts the thread without any
> exception handling.
> 
> Now the question is how the precompiled
> DLL on the net was compiled.

The precompiled DLL was built using MSVC and is using SEH.
The C++ EH is in there to support building the library
with the GNU compilers. The third option (ie. build with C
and no EH) perhaps shouldn't be there, although, provided
people are aware of the limitations could be useful to
someone.

Side note: the EH within the DLL should be self-contained
such that an application which uses the library can be
built as standard C without EH and not run into trouble.
At least that is what I've been assuming. I could be wrong.

Ross

RE: cancelling

[Bossom, John]

Check to see if the code base for pthread is wrapping
an exception handler around your thread mainline
(the original code had an internal routine called "threadStart"
which used Microsoft's Structured Exception Handling for catching all
exceptions raised in your thread.)
The cancel mechanism was implemented using this strategy.
Now, your thread is recognizing the cancel (the exception
hex value is human readable: BAD DEED) and should have
been caught by the threadStart wrapper, which would have
gracefully shut down your thread.

I am not familiar with the code base anymore so you will
have to ask others... ie Ross

-----Original Message-----
From: Thomas Sailer [ mailto:sailer@ife.ee.ethz.ch ]
Sent: Monday, July 10, 2000 11:55 AM
To: pthreads-win32@sourceware.cygnus.com
Subject: cancelling


I'm trying to cancel a thread that is blocking
in pthread_cond_wait. When I do this, I get:
gdb: unknown target exception 0xebaddeed at 0x77e79b01

I'm using the precompiled snapshot 1999-11-02,
the rest of the program is compiled with the current
(as of two weeks ago) cygwin gcc (with -mno-cygwin).

What am I missing?

Tom

Re: cancelling

[Thomas Sailer]

"Bossom, John" wrote:

> Check to see if the code base for pthread is wrapping
> an exception handler around your thread mainline
> (the original code had an internal routine called "threadStart"
> which used Microsoft's Structured Exception Handling for catching all
> exceptions raised in your thread.)

The thread I'm trying to cancel was created with pthread_create,
and internally the thread routine is started through
_pthread_threadStart, which should be fine.

The thread that tries to cancel is the initial thread, i.e.
the one that called _main.

> Now, your thread is recognizing the cancel (the exception
> hex value is human readable: BAD DEED) and should have

I thought that the constant wasn't chosen arbitrarily :))

Tom

cancelling

[Thomas Sailer]

I'm trying to cancel a thread that is blocking
in pthread_cond_wait. When I do this, I get:
gdb: unknown target exception 0xebaddeed at 0x77e79b01

I'm using the precompiled snapshot 1999-11-02,
the rest of the program is compiled with the current
(as of two weeks ago) cygwin gcc (with -mno-cygwin).

What am I missing?

Tom