>
> I don't understand exactly what you are saying. When you say
> "with usage pthreads-win32", what do you mean?
http://sourceware.org/pthreads-win32/
If you are trying to use pthreads-win32 to get std::thread working
> with mingw-w64, I gave some instructions in an earlier post:
>
> http://s
Hello niXman!
On Fri, Sep 30, 2011 at 12:04 AM, niXman wrote:
> I have rebuilt with usage pthreads-win32 - there was other error. In
> general I was tangled...
I don't understand exactly what you are saying. When you say
"with usage pthreads-win32", what do you mean?
When you say "in general I
I have rebuilt with usage pthreads-win32 - there was other error. In
general I was tangled...
I will ask once again: Somebody tried to understand in what the bug reason?
niXman.
2011/9/28 niXman :
> Hi Frank.
>
>>
>> (niXman... Is that supposed to be some kind of superhero?)
>
> No. It`s from th
Hi Frank.
> (niXman... Is that supposed to be some kind of superhero?)
No. It`s from the "Man who always uses the *nix" platform =)
niXman, if your use case is to use std::thread with mingw-w64 and
> pthreads-win32, I should be able to refer you to some earlier posts that
> show how to do it,
Hello Ruben and niXman!
(niXman... Is that supposed to be some kind of superhero?)
On Wed, Sep 28, 2011 at 1:22 PM, Ruben Van Boxem
wrote:
> 2011/9/28 niXman
>>>
>>> It is a known problem and probably due to an operation libstdc++ does
>>> when
>>> std::thread is used that winpthreads doesn't
>
> No, you can't use std::thread with pthreads-win32. It doesn't support all
> the required functionality.
Nonetheless, I'll try and I'll notify you about the results.
That is not only impossible, it wouldn't be right. This would allow
> mulltiple instances of winpthreads (the statically linked
2011/9/28 niXman
> It is a known problem and probably due to an operation libstdc++ does when
>> std::thread is used that winpthreads doesn't like but should allow. I don't
>> know how to fix this, sorry. Maybe Kai or JonY have more ideas on the
>> matter.
>>
>> Ruben
>>
>> Hi Ruben!
>
> Tell me,
>
> It is a known problem and probably due to an operation libstdc++ does when
> std::thread is used that winpthreads doesn't like but should allow. I don't
> know how to fix this, sorry. Maybe Kai or JonY have more ideas on the
> matter.
>
> Ruben
>
> Hi Ruben!
Tell me, if I use pthread-win32 ins
Op 28 sep. 2011 01:03 schreef "niXman" het volgende:
>
> Hi all!
> I met such a problem: I've been building MinGW with --disable-shared, and
everything went well untill I understood that exceptions from DLL aren't
catched in the main program.
> Example. The program terminates with message: termina
Example:
int main() {
std::mutex mutex;
std::condition_variable cond;
std::unique_lock lock(mutex);
cond.wait_for(lock, std::chrono::milliseconds(1000)); // <<
SIGSEGV
}
Backtrace:
Program received signal SIGSEGV, Segmentation fault.
0x in ?? ()
(gdb) backtrace
#0
Hi all!
I met such a problem: I've been building MinGW with --disable-shared, and
everything went well untill I understood that exceptions from DLL aren't
catched in the main program.
Example. The program terminates with message: terminate called after
throwing an instance of 'int
DLL:
void func()
11 matches
Mail list logo
