Re: [bug] possible condition depending on uninitialized value in _notmuch_message_sync

2022-05-24 Thread Eliza Velasquez
On Fri, May 20 2022 at 09:46 -03, David Bremner wrote: > Eliza Velasquez writes: > >> On Mon, May 16 2022 at 06:47 -03, David Bremner wrote: >> >>> Ideally of course I'd like a reproducer in C. It would help to have >>> line numbers in the valgrind output. It might be enough you install the

Re: [bug] possible condition depending on uninitialized value in _notmuch_message_sync

2022-05-20 Thread David Bremner
Eliza Velasquez writes: > On Mon, May 16 2022 at 06:47 -03, David Bremner wrote: > >> Ideally of course I'd like a reproducer in C. It would help to have >> line numbers in the valgrind output. It might be enough you install the >> notmuch debug symbols? > > Took me a while to figure out the

Re: [bug] possible condition depending on uninitialized value in _notmuch_message_sync

2022-05-16 Thread David Bremner
Eliza Velasquez writes: > It becomes very clear why this error only happens when removing a > non-existent tag if you look at at message.cc:1570... > > --8<---cut here---start->8--- > try { > message->doc.remove_term (term); >

Re: [bug] possible condition depending on uninitialized value in _notmuch_message_sync

2022-05-16 Thread Eliza Velasquez
On Mon, May 16 2022 at 06:47 -03, David Bremner wrote: > Ideally of course I'd like a reproducer in C. It would help to have > line numbers in the valgrind output. It might be enough you install the > notmuch debug symbols? Took me a while to figure out the debugging workflow in NixOS, but I

Re: [bug] possible condition depending on uninitialized value in _notmuch_message_sync

2022-05-16 Thread David Bremner
Eliza Velasquez writes: > Is it possible then that there's a potential memory error with removing > a non-existent tag on a message? I wanted to ask about this on the > mailing list before diving in deeper, since this isn't quite the latest > version of notmuch and I wasn't sure if it had been