[JDEV] Re: jabberd 1.4.3 release candidate again

[Frank Seesink]

Frank Seesink wrote:
> Downloaded latest CVS with all the newest Cygwin changes.  It 
> compiles/runs great!  Thanks very much.  Hope this helps others as much 
> as it does me.
> 
> Now if I could just figure out the debug mode issue, this would be 
> perfect.  But don't let that hold things up.  I suspect the debug mode 
> segfaults are due to some pth/fork() issue, which means a real change in 
> code (which I have not touched to date...only how to compile/link). 
> Those under Cygwin will have to live without using -D for the time 
> being, as I suspect the fix for this may require much more time.  And 
> hopefully by then Jabberd2 will up and running cleanly.

Ok, I admit it.  I'm kind of on a mission.  At this point Jabberd 
1.4.3CVS compiles/links/runs the same under Cygwin as it does on other 
*nix platforms, with the one exception of running in debug mode (using 
the -D switch).

So let me ask this, as I'm just starting to dig into the source code 
itself.  Can anyone steer me in the right direction as to why, whenever 
I attempt to fire up Jabberd in debug mode, I see the following:
____________________________________________________________
$ ./jabberd/jabberd.exe -D
Sat Nov  8 18:44:11 2003  mio.c:787 MIO is starting up
Sat Nov  8 18:44:11 2003  mio.c:816 mio while loop top
**Pth** STACK OVERFLOW: thread pid_t=0xa040750, name="unknown"
Segmentation fault
____________________________________________________________

This happens regardless of whether I have configured/built jabberd with 
(--enable-ssl) or without SSL support.  So I've ruled that out at least. 
  It fails with the generic jabber.xml config.  Basically, I have not 
been able to get Jabberd to fire up if I use the -D switch.

The actual pid_t number may vary (haven't been paying enough attention 
to notice if it changes or if there's a pattern to be honest), but the 
sequence of messages is always the same.  Jabberd starts and dies in the 
blink of an eye.

However, simply NOT running in debug mode avoids ALL this, and I've had 
a Jabber server running for weeks at a time in production (granted, low 
user load, but still), usually only restarting when I reboot the Windows 
XP Pro box it's running on.

Has anyone else experienced this kind of behavior on any other platform? 
   Any insight into where to look?  I realize running Cygwin under 
Windows, I'm working in a cludged environment at best.  But figured it 
best to ask you good folks if you've ever seen this before, as you might 
save me a great deal of time in finding the source of the problem...even 
if the end result is just "It's a limitation of Cygwin/Windows.  Suck it 
up." :-)

In the meantime, the hunt continues...