Hi, Sergey, Thanks for the useful info! Obviously, you've tired to the ease the way for troubleshooting -- very nice.
> This however makes little sense for debugging, because imap4d will fork > off a child for each incoming connection. There are two approaches to > debug what's going on in a child. I haven't tried, but I think there might now be a 3rd way, using gdb with 'set follow-fork-mode child' and 'start' mode, or whatever its called where gdb runs the C startup code and stops just before calling main. Might have to restart the running imap4d after attaching to it, though. But I'll definitely be filing this email away for (hopefully unneeded) future reference. Now -- the wonders of global projects! Apparently the new version is so very new, its in the future (at least , thats what my server is trying to tell me.) :D ## ----------- ## ## Core tests. ## ## ----------- ## configure:2949: checking for a BSD-compatible install configure:3017: result: /usr/bin/install -c configure:3028: checking whether build environment is sane configure:3083: error: newly created file is older than distributed files! Check your system clock Haven't decided yet how to handle this. Thanks, Chris _______________________________________________ Bug-mailutils mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-mailutils
