Hi,
On Saturday 30 September 2017 16:24:57 René J. V. Bertin wrote:
> Konrad Rosenbaum wrote:
> > Apart from this I'd suspect you will still get the SEGV if you do not
> > block - even if the frequency changes.
>
> As in when emitting the signal too frequently from multiple threads?
No. as in
Simon just gave a talk about signals and slots on different threads and
the internals of how Qt handles this at CppCon in Seattle yesterday. I
would suggest you have a look at the video of his presentation when it
comes out. You could also look at the documentation:
Konrad Rosenbaum wrote:
> Apart from this I'd suspect you will still get the SEGV if you do not block
> - even if the frequency changes.
As in when emitting the signal too frequently from multiple threads?
For my personal education, what happens behind the scenes when a signal is sent
from one
Konrad Rosenbaum wrote:
> You do know what a thread is - right? ;-)
Yeah, my momma taught me long ago ;)
> Sorry, I'm too lazy/busy to read the source right now to make sure that no
> signal handlers are used here.
No problem, it was just curiosity.
> Apart from this I'd suspect you will
On Saturday 30 September 2017 11:31:13 René J. V. Bertin wrote:
> Thiago Macieira wrote:
[about internal mutex]
> > You cannot, because neither the kqueue, inotify or poll backends do
> > that.
> > Those three have no mutexes at all. You have to block the event loop of
> > the thread they were
Thiago Macieira wrote:
>> >> How does QFSW handle a situation in which an already watched directory is
>> >> changed while another directory is being added? SNIP
>> >
>> > The Darwin implementation has an internal mutex so that the dispatcher
>> > thread (I'm assuming) is able to get to the
