Wondering if this is a known issue, I'm working on a little pet project
of mine (http://github.com/rtyler/imuse/) and I'm starting just by
working through code in mtest.c and pushing it into CUnit tests to make
sure I'm actually understanding what's going on here.

You can see my test here:
http://github.com/rtyler/imuse/raw/887927b457d7c023f3c420c401d78fd527a6c299/tests/smtp.c

The meat of it is test_BasicSendMail() which is almost verbatim
mtest.c:smtpsend().

Both mtest.c and my own smtp.c test code SIGSEGV when they enter
smtp_close(), leaving the following output when I run it via gdb:
        (gdb) run
        Starting program: /home/tyler/source/github/imuse/tests/smtp 
        [Thread debugging using libthread_db enabled]
        
        
             CUnit - A Unit testing framework for C - Version 2.1-0
             http://cunit.sourceforge.net/
        
        
        Suite: Smtp_Suite
          Test: empty test ... passed
          Test: sending a basic email ... ==(mm_log)==> Trying IP address 
[10.10.1.10]
        Sending...
        Okay, 250 2.0.0 Ok: queued as 2C50F3898060
        
        Program received signal SIGSEGV, Segmentation fault.
        0x00007ffff6a52c25 in free () from /lib64/libc.so.6
        (gdb) 
        
I'm running openSUSE 11.1/amd64. and my c-client/imaplib code come from
openSUSE's "imap-devel" and "imap-lib" packages.

Anybody know why this is occurring? I'd appreciate any pointers (pun
totally intended).

Cheers, 
-R. Tyler Ballance

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
Imap-uw mailing list
[email protected]
http://mailman2.u.washington.edu/mailman/listinfo/imap-uw

Reply via email to