Re: Unexplained Segmentation Fault

2004-05-15 Thread Ken Murchison
Actually, I wanted a backtrace of the stack via a debugger, eg, run gdb on the imtest core file. Guilden Crantz wrote: Here is the stack trace (password removed): [EMAIL PROTECTED] src]# strace imtest -t "" menagerie.cc execve("/usr/local/bin/imtest", ["imtest", "-t", "", "menagerie.cc"], [/*

Re: Unexplained Segmentation Fault

2003-07-15 Thread Rob Siemborski
On Tue, 15 Jul 2003 [EMAIL PROTECTED] wrote: > > > That being said, try upgrading to a more recent version of SASL (eg, > > 2.1.14). There have been a lot of bugfixes since 2.1.7. > > > > taking your advice I have tried to install sasl 2.1.14, but I can't get > it to come compile. DAH! Apply th

Re: Unexplained Segmentation Fault

2003-07-14 Thread guildencrantz
> That being said, try upgrading to a more recent version of SASL (eg, > 2.1.14). There have been a lot of bugfixes since 2.1.7. > taking your advice I have tried to install sasl 2.1.14, but I can't get it to come compile. DAH! I configured it with: ./configure --disable-gssapi --enable-pwc

Re: Unexplained Segmentation Fault

2003-07-14 Thread Guild N Crantz
DOH! Sorry about that, here's the backtrace: [EMAIL PROTECTED] root]# gdb imtest core.23103 GNU gdb Red Hat Linux (5.2.1-4) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of i

Re: Unexplained Segmentation Fault

2003-07-14 Thread Ken Murchison
You need to do a backtrace command (bt) while in the debugger. That being said, try upgrading to a more recent version of SASL (eg, 2.1.14). There have been a lot of bugfixes since 2.1.7. Guilden Crantz wrote: Okay, here's the gdb core dump analysis: [EMAIL PROTECTED] root]# gdb imtest core.23

Re: Unexplained Segmentation Fault

2003-07-13 Thread Guilden Crantz
Okay, here's the gdb core dump analysis: [EMAIL PROTECTED] root]# gdb imtest core.23103 GNU gdb Red Hat Linux (5.2.1-4) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it und

Re: Unexplained Segmentation Fault

2003-07-13 Thread Ken Murchison
Actually, I wanted a backtrace of the stack via a debugger, eg, run gdb on the imtest core file. Guilden Crantz wrote: Here is the stack trace (password removed): [EMAIL PROTECTED] src]# strace imtest -t "" menagerie.cc execve("/usr/local/bin/imtest", ["imtest", "-t", "", "menagerie.cc"], [/*

Re: Unexplained Segmentation Fault

2003-07-12 Thread Guilden Crantz
Here is the stack trace (password removed): [EMAIL PROTECTED] src]# strace imtest -t "" menagerie.cc execve("/usr/local/bin/imtest", ["imtest", "-t", "", "menagerie.cc"], [/* 20 vars */]) = 0 uname({sys="Linux", node="ophelia.menagerie.cc", ...}) = 0 brk(0) =

Re: Unexplained Segmentation Fault

2003-07-12 Thread Igor Brezac
What is your 'ulimit -n'? imtest dumps when max file descriptors is set higher than 1024 (at least it does on Solaris)... -Igor On Sat, 12 Jul 2003, Ken Murchison wrote: > It looks like imtest is dumping core, not imapd. If you post a stack > trace of imtest, we might be able to provide some

Re: Unexplained Segmentation Fault

2003-07-12 Thread Ken Murchison
It looks like imtest is dumping core, not imapd. If you post a stack trace of imtest, we might be able to provide some help. Guilden Crantz wrote: I have been diging and digging through the Cyrus SASL and IMAP documents, but I can not find the error. Any suggestions would be greatly appreciated

Unexplained Segmentation Fault

2003-07-12 Thread Guilden Crantz
I have been diging and digging through the Cyrus SASL and IMAP documents, but I can not find the error. Any suggestions would be greatly appreciated. Running: RedHat 8, Cyrus SASL 2.1.7, Cyrus 2.1.14 I'm simply trying to authenticate against /etc/passwd [EMAIL PROTECTED] imap]# imtest -t "" m