Closed Bug 6527 Opened 25 years ago Closed 23 years ago

testimap dumps core when I run an IMAP command

Categories

(MailNews Core :: Backend, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: sspitzer, Assigned: mscott)

Details

testimap crashes on linux [sspitzer.mcom.com (linux 2.2.7)] log: Starting program: /builds/sspitzer/MOZILLA/05.15.1999/04.30/mozilla/dist/bin/testimap Enter command number: 0 Commands currently available: 0) List available commands. 1) Run IMAP Command. 2) Check identity information. 3) Test url parsing. 4) Select Folder. 5) Download a message. 9) Exit the test application. Enter command number: 2 ProfileName : default ProfileDir : /u/sspitzer/.mozilla/Users50/Default accountList = account0,account3,account4,account2,account1 accountKey = account0 Loading preferences for account: account0 accountKey = account3 Loading preferences for account: account3 accountKey = account4 Loading preferences for account: account4 accountKey = account2 Loading preferences for account: account2 accountKey = account1 Loading preferences for account: account1 Imap Server: tintin User Name: sspitzer Imap Password: <removed> Enter command number: 1 Enter IMAP command to run [capability]: Program received signal SIGUSR1, User defined signal 1. here's the stack trace: #0 0x4078bf54 in __syscall_sigsuspend () #1 0x407b049c in __DTOR_END__ () #2 0x4044c5dd in pthread_create (thread=0xbffff860, attr=0xbffff868, start_routine=0x40436b68 <_pt_root>, arg=0x8075bc8) at restart.h:32 #3 0x40437242 in _PR_CreateThread (type=PR_USER_THREAD, start=0x408051a0 <nsImapProtocol::ImapThreadMain(void *)>, arg=0x8099078, priority=PR_PRIORITY_NORMAL, scope=PR_GLOBAL_THREAD, state=PR_UNJOINABLE_THREAD, stackSize=65536, isGCAble=0) at ptthread.c:374 #4 0x4043745f in PR_CreateThread (type=PR_USER_THREAD, start=0x408051a0 <nsImapProtocol::ImapThreadMain(void *)>, arg=0x8099078, priority=PR_PRIORITY_NORMAL, scope=PR_LOCAL_THREAD, state=PR_UNJOINABLE_THREAD, stackSize=0) at ptthread.c:457 #5 0x40804348 in nsImapProtocol::Initialize (this=0x8099078, aHostSessionList=0x80adeb8, aSinkEventQueue=0x80524a8) at nsImapProtocol.cpp:268 #6 0x40820dca in nsImapService::CreateImapConnection (this=0x807e450, aEventQueue=0x80524a8, aImapUrl=0x0, aImapConnection=0x8052c2c) at nsImapService.cpp:172 #7 0x804b3cd in nsIMAP4TestDriver::InitializeProtocol (this=0x80525a0, urlString=0x80527a0 "imap://nsmail-2.mcom.com/?capability") at imapProtocolTest.cpp:258 #8 0x804bf64 in nsIMAP4TestDriver::OnRunIMAPCommand (this=0x80525a0) at imapProtocolTest.cpp:524 #9 0x804b6be in nsIMAP4TestDriver::ReadAndDispatchCommand (this=0x80525a0) at imapProtocolTest.cpp:326 #10 0x804b5c3 in nsIMAP4TestDriver::RunDriver (this=0x80525a0) at imapProtocolTest.cpp:285 #11 0x804c70e in main () at imapProtocolTest.cpp:724
Status: NEW → ASSIGNED
Target Milestone: M7
thanks seth...we actually never intended for the test app to really run on linux (although it could). we were just using it as a crutch to get imap going on windows. if it's any consolation, the test app has bit rotted on windows too and no longer runs there.. we can look at geting it running but it doesn;t buy us much...so i yhink it is low priority....setting to m7...
thanks for the info. I agree, this is a low priority bug.
QA Contact: 4080 → 4098
Target Milestone: M7 → M8
I talked to Phil about this and we're going to move it to M8. The imap test app has been pretty neglected and has runtime problems beyond just Linux (i.e. non platform specific problems). M8 =).
Target Milestone: M8 → M11
test app no longer functional at all - need to push this off.
OS: Linux → All
Hardware: PC → All
changing platform to All since, in general, the imap test program needs revamping. Will we have a need for an IMAP test program as this product gets towards beta?
it would be nice to have, but it's not clear that getting the test program working again is ever going to be more important than fixing bugs in the actual product :-(
Target Milestone: M11 → M15
Triage to M15
QA Contact: scurtis → huang
Change QA Contact to me since it's my feature now.
testimap doesn't even run anyway....no one uses it anyway....
Target Milestone: M15 → M20
should we just close this out?
I removed the stand alone news tests from the build, and cvs removed it. if testimap is rotten, or no longer used, we should just remove it.
testimap is long gone.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
v. testimap is no more.
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.