an error causes Alpine to quit!

Rob Pyott

unread,

Feb 13, 2021, 4:42:22 PM2/13/21

to

Sorry to post so much at once. Appreciate the expertise.

I received this error today after deleting 150+ messages in my Junk folder. The message is shown after Alpine crashes/quits. Any suggestions? Thanks.... Rob

Last login: Sat Feb 13 07:38:08 on ttys000
albertpyott@ARP-mini ~ % alpine

Problem detected: "Bad msgno 0 in mail_elt, nmsgs = 0, mbx={imap.mail.me.com.akadns.net:993/imap/nostarttls/ssl/user="pyott"}Junk".
Alpine Exiting.
zsh: abort alpine
albertpyott@ARP-mini ~ % ,,q
albertpyott@ARP-mini ~ % alpine

Eduardo Chappa

unread,

Feb 14, 2021, 4:08:00 AM2/14/21

to

On Sat, 13 Feb 2021, Rob Pyott wrote:

> Sorry to post so much at once. Appreciate the expertise.
>
> I received this error today after deleting 150+ messages in my Junk folder. The message is shown after Alpine crashes/quits. Any suggestions? Thanks.... Rob
>

> Problem detected: "Bad msgno 0 in mail_elt, nmsgs = 0, mbx={imap.mail.me.com.akadns.net:993/imap/nostarttls/ssl/user="pyott"}Junk".
> Alpine Exiting.

Could you repeat this crash one more time, but execute Alpine under gdb
and send us the output of the

(gdb) bt

comand?

Thank you

--
Eduardo
https://tinyurl.com/yc377wlh (web)
http://repo.or.cz/alpine.git (Git)

Rob Pyott

unread,

Feb 14, 2021, 12:29:10 PM2/14/21

to

Not sure if I'm using gdb right. I got this:

(gdb) file /usr/local/Cellar/alpine/2.24/bin/alpine
Reading symbols from /usr/local/Cellar/alpine/2.24/bin/alpine...
(No debugging symbols found in /usr/local/Cellar/alpine/2.24/bin/alpine)
../../gdb/thread.c:95: internal-error: struct thread_info *inferior_thread(): Assertion `current_thread_ != nullptr' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) y

This is a bug, please report it. For instructions, see:
<https://www.gnu.org/software/gdb/bugs/>.

../../gdb/thread.c:95: internal-error: struct thread_info *inferior_thread(): Assertion `current_thread_ != nullptr' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) n

Eduardo Chappa

unread,

Feb 14, 2021, 6:13:44 PM2/14/21

to

On Sun, 14 Feb 2021, Rob Pyott wrote:

> Not sure if I'm using gdb right. I got this:
>
> (gdb) file /usr/local/Cellar/alpine/2.24/bin/alpine
> Reading symbols from /usr/local/Cellar/alpine/2.24/bin/alpine...
> (No debugging symbols found in /usr/local/Cellar/alpine/2.24/bin/alpine)

Your version of Alpine was not built with debug support. You need to find
one that has debug support so you can reproduce the problem.

Carlos E.R.

unread,

Feb 14, 2021, 7:08:07 PM2/14/21

to

On 15/02/2021 00.13, Eduardo Chappa wrote:
> On Sun, 14 Feb 2021, Rob Pyott wrote:
>
>> Not sure if I'm using gdb right. I got this:
>>
>> (gdb) file /usr/local/Cellar/alpine/2.24/bin/alpine
>> Reading symbols from /usr/local/Cellar/alpine/2.24/bin/alpine...
>> (No debugging symbols found in /usr/local/Cellar/alpine/2.24/bin/alpine)
>
> Your version of Alpine was not built with debug support. You need to
> find one that has debug support so you can reproduce the problem.
>

Depending on the distro, the debug information could be on another
repository; that's what openSUSE does. One has to add the debug repo,
and gdb prints an error message that tells the exact zypper command to
install what is missing. Cool :-)

But it seems Rob is using a local build :-?

--
Cheers, Carlos.

Rob Pyott

unread,

Feb 14, 2021, 7:29:26 PM2/14/21

to

I'm using the build prepared for mac -- it's from the Homebrew repository. I don't know how to add a debug repo :(

I'm not sure I can repeat the error at this point though. I occurred when I was deleting a lot of junk mails. So those 150+ items are gone and things seem to be running ok.