Hmm, this is the second such SIGABRT bug to come in in a few days (the first was bug 924703). Pity about the lack of readable stack information.
Hmm, this is the second such SIGABRT bug to come in in a few days (the first was bug 924703). Pity about the lack of readable stack information.