Replying to myself: Inside the runtime loader, the call that fails is _kern_create_area(). More specifically, this code: Line 938 if (image->regions[i].flags & RFLAG_ANON) { image->regions[i].id = _kern_create_area(regionName, (void **)&loadAddress, addressSpecifier, image->regions[i].vmsize, B_NO_ LOCK, B_READ_AREA | B_WRITE_AREA); if (image->regions[i].id < 0) { status = image->regions[i].id; goto error; } image->regions[i].delta = loadAddress - image->regions[i]. vmstart; image->regions[i].vmstart = loadAddress; } Again, this only happens as described in the previous email (and below) . -Bruno On Tue, 24 Feb 2009 14:57:43, Bruno Albuquerque said: > It seems that there is an interaction between the new OpenSSL > libraries, MDR protocol add-ons and the runtime loader. Here is how > it > happens: > > 1 - When you first create an account, it defaults to POP3 as the > protocol. If you switch the protocol to IMAP, the preferences panel > crashes (more about this below). > 2 - If I change the email preferences to default to IMAP as the > protocol, it does nto crash when switching to POP3 neither when > switching back to POP3, but if I save the account as POP3 and close > and > reopen the preferences panel and try to switch to IMAP, it crashes. > > The crash mentioned happens because load_add_on() fails (with a > General > OS Error) when trying to load the IMAP add-on. Syslog just shows > this: > > KERN: runtime_loader: Could not map image: Invalid Argument > > As seem above, this happens only if POP3 is loaded first (with load_ > add > _on()) and then IMAP is loaded (also with load_add_on()). If the > order > is reversed, there is no crash. It also only happens with the most > recent SSL version (not with the previous version). > > Any ideas? Ingo, any suggestions about trying to debug this at the > runtime_loader level? > > -Bruno >