New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Runtime error when invoking complete in save-entry #4178
Comments
That appears to be a message from ubsan, at the indicated line I'm not entirely certain how this complete function is supposed to function, but I believe it would be relatively simple to add a simple check for the case of 0 length. |
Thanks for the bug report; I haven't had a chance to investigate yet. As you've already noted, a simple check would stop the problem. However... What I'd love to know is why we're getting a If someone has a bit of time to dig into the code, it'd really be appreciated. Thanks! |
I can't seem reproduce this. With ubsan enabled I actually get a different error on every completion, not just empty. Maybe because I'm on macOS.
Which I can fix with:
|
Expected Behaviour
Invoking
complete-query
insave-entry
(called from Attachments view) shouldn't emit runtime error message.Actual Behaviour
When pressing
<Tab>
(trying to invoke complete via bindingbind editor <Tab> complete-query
) on an emptysave-entry
prompt results in following message (butneomutt
doesn't crash)Steps to Reproduce
v
enterAttachments
view on any messages
opensave-entry
prompt./
inserted, so delete it to obtain an empty promptcomplete-query
(for example with<Tab>
and binding mentioned earlier) results in the error messageHow often does this happen?
My limited testing suggests that it happens always, but only on the first try after opening
neomutt
.When did it start to happen?
I noticed it already on the previous release NeoMutt 2023-12-21.
NeoMutt Version
The text was updated successfully, but these errors were encountered: