Re: [Boost-users] Crashing Issue

Subject: Re: [Boost-users] Crashing Issue
From: Vicente J. Botet Escriba (vicente.botet_at_[hidden])
Date: 2015-11-04 07:07:15

Le 05/02/15 15:30, Nat Goodspeed a écrit :
>>> On Wed, Feb 4, 2015 at 12:10 AM, Vicente J. Botet Escriba
>>> <vicente.botet_at_[hidden]> wrote:
>>>> it could help if you post the example and the backtrace.
>>>>
>>>> Which version/OS/compiler use others for which this works?
> On Wed, Feb 4, 2015 at 7:52 PM, swati upadhyaya
> <swatiupadhyaya_at_[hidden]> wrote:
>
>> hi I am using like this where RunningThreads_ is vector containing boost
>> thread object pointer(handler).I am using interrupt() for the interruption
>> of thread interruption_point() catching that interruption then
>> joining.everytime its crashing in join() for me but for others who have the
>> same configuration its working fine all of us has windos 8. For me also it
>> was working last week but this week the same piece of code is crashing. :(
>>               RunningThreads_[i].handle->interrupt();
>>
>>              RunningThreads_[i].handle->join();
>>
>>              delete RunningThreads_[i].handle;
> I'm pretty sure Vicente meant: please either paste or attach a
> complete small program source, with all relevant #includes, that he
> could download or paste into a local file and immediately compile
> himself to observe the problem.
>
> Very often a problem we observe strongly depends on the context in
> which the relevant statements are running.
>
> Sometimes the very process of deriving the smallest program that still
> fails is sufficient to solve the problem yourself. Highly recommended.
>
> Sometimes, if every small example program you create (without your own
> organization's code) behaves exactly as expected, you establish that
> the problem really isn't in the Boost library.
>
> If you can send a _small_ program that replicates the problem, you
> give the library author some chance of diagnosing the issue without
> having to spend days untangling your control flow.
>
> For all of these reasons: whittle down the problem to the smallest
> possible complete, self-contained program that demonstrates the
> problem.
>
>
Thanks a lot Nat for clarifying what is needed to help the tired 
maintainers as me ;-)

Best,
Vicente