On Wed, Apr 28, 2010 at 12:59 AM, Matthias Clasen
wrote:
> I have now fixed up the docs for GtkContainer and for GtkLabel
> width-chars and max-width-chars and fixed the few remaining
> regressions that I found.
I've merged this now. Let me know if you spot any regressions.
__
On 2010-04-30 13:38, Matthew Bucknall wrote:
> Find attached an excerpt from an application of mine. Not entirely
> self-contained, but you should get a general idea of what is going on.
>
> Using the attached code, my application calls app_signal_block_unused()
> early on during initialization. T
Find attached an excerpt from an application of mine. Not entirely
self-contained, but you should get a general idea of what is going on.
Using the attached code, my application calls app_signal_block_unused()
early on during initialization. The signal listening thread is
initialized and started b
On Fri, 2010-04-30 at 11:02 -0500, Stef Walter wrote:
> 1. Block signals you're interested in on all threads, usually done
> early on, before starting any threads. Using pthread_sigmask.
How do you block signals in all threads before starting any thread ?
Oh well, I guess looking at how you d
On 2010-04-30 10:51, Stef Walter wrote:
> On 2010-04-30 08:53, Richard Hughes wrote:
>> On 30 April 2010 14:36, Stef Walter wrote:
>>> Remember that this doesn't work correctly in threaded apps, as we found
>>> in gnome-keyring-daemon. You have to do the strange
>>> signal-handling-thread-thing.
>
On 2010-04-30 08:53, Richard Hughes wrote:
> On 30 April 2010 14:36, Stef Walter wrote:
>> Remember that this doesn't work correctly in threaded apps, as we found
>> in gnome-keyring-daemon. You have to do the strange
>> signal-handling-thread-thing.
>
> Could you give more details please? Thanks
On Fri, 2010-04-30 at 08:36 -0500, Stef Walter wrote:
> Remember that this doesn't work correctly in threaded apps, as we found
> in gnome-keyring-daemon. You have to do the strange
> signal-handling-thread-thing.
create a thread and sigwait in it in the hope that no other thread does
the same.
On Fri, 2010-04-30 at 09:18 +0100, Richard Hughes wrote:
> I'm writing for comments. Making my daemons (upower, PackageKit, etc)
> quit nicely after receiving SIGTERM or SIGINT is _really_ hard to do
> correctly. The fact that I can only do a few things (write, etc) in
> the signal handler makes ot
On 30 April 2010 14:36, Stef Walter wrote:
> Remember that this doesn't work correctly in threaded apps, as we found
> in gnome-keyring-daemon. You have to do the strange
> signal-handling-thread-thing.
Could you give more details please? Thanks.
Richard.
On 2010-04-30 03:56, Andy Wingo wrote:
> On Fri 30 Apr 2010 10:23, Xavier Bestel writes:
>
>> On Fri, 2010-04-30 at 09:18 +0100, Richard Hughes wrote:
>>> I'm writing for comments. Making my daemons (upower, PackageKit, etc)
>>> quit nicely after receiving SIGTERM or SIGINT is _really_ hard to do
From: "Andy Wingo", Date: 30/04/2010 19:01
> On Fri 30 Apr 2010 10:23, Xavier Bestel ; writes:
>> On Fri, 2010-04-30 at 09:18 +0100, Richard Hughes wrote:
>>> I'm writing for comments. Making my daemons (upower, PackageKit, etc)
>>> quit nicely after receiving SIGTERM or SIGINT is _really_ hard to
On Fri 30 Apr 2010 10:23, Xavier Bestel writes:
> On Fri, 2010-04-30 at 09:18 +0100, Richard Hughes wrote:
>> I'm writing for comments. Making my daemons (upower, PackageKit, etc)
>> quit nicely after receiving SIGTERM or SIGINT is _really_ hard to do
>> correctly. The fact that I can only do a f
On Fri, 2010-04-30 at 09:18 +0100, Richard Hughes wrote:
> I'm writing for comments. Making my daemons (upower, PackageKit, etc)
> quit nicely after receiving SIGTERM or SIGINT is _really_ hard to do
> correctly. The fact that I can only do a few things (write, etc) in
> the signal handler makes ot
On 30 April 2010 09:23, Xavier Bestel wrote:
> Can't you just signal your mainloop to quit from the signal handler, and
> do the heavyweight work from there ?
That's what I'm doing right now, but I've been told that's not safe.
If it is, then it's much less work for me.
Richard.
I'm writing for comments. Making my daemons (upower, PackageKit, etc)
quit nicely after receiving SIGTERM or SIGINT is _really_ hard to do
correctly. The fact that I can only do a few things (write, etc) in
the signal handler makes otherwise quite nice GLib code very quickly
descend into l33t UNIX
15 matches
Mail list logo
