[OT] Question about nanosleep

[walt]

Simon 'corecode' Schubert wrote:
walt wrote:
...Does DragonFly implement nanosleep, and if not, why not?
Yes, it does. There was just a bug in its code for signals. Fixed in
55d25c8782a76b25372313a908dff0a66d6ff342.
Yes, the test code works now, thanks!

You were foolish enough to respond to my question, so here's another one
for you ;o)
The way I spotted the failure of the nanosleep test on my amd64 linux
machine was that the 'configure' script hung (hanged?) forever while
running the nanosleep 'conftest' executable.
The part of this puzzle I don't understand is that the 'configure' code in
question hangs *only* when run in a gnome session(!).  If I run that same
code from a virtual-terminal or e.g. a kde session, it returns 119 in one
second (as I would expect from reading the code), but at least it returns
instead of hanging forever.
I'm hoping someone can offer a theory to explain why the gnome session acts
differently from other X desktops (and only on a 64-bit OS). Signals, maybe?
Another hint:  when I'm running a gnome session, I can't kill an app with
Ctrl-C when I start it from an xterm.  I see ^C appear on the xterm, but the
app never gets the message, and so it never stops.
No theories too bizarre to consider, thanks!