Jason Ornstein <jason.ornstein@sybase.com> wrote:
I've worked around some of the compile time issues that I'm having and now I have something that is a bit more of a problem. I've configured the server with --enable-developer and I'm running the server with gdb (this happens without gdb too) and this is part of what I see: ...
I'm seriously hacking much of the server core, so it's not overly tested.
Am I wrong in thinking, that in a normal case I should see some type of backtrace?
You should see a backtrace.
Maybe listener is never NULL?
It works in my sandbox, not that it says much... I'd suggest using: fprintf(stderr, "%s[%d]\n", __FILE__, __LINE__); in various places, down the call chain, until you don't see the messages. The point right before that is where it's dying. :) Also, if you're doing a "cvs update", you might want to "make clean;make". I've discovered that the dependencies in the Makefile aren't correct, and doing a "make" sometimes doesn't re-build things it should. Alan DeKok.