~tardypad/wee-most-discuss

1

Possible problem with SIGSEGV in weechat caused that seems to be caused by wee_most.py

Per-Arne Hellarvik <duckboot@gmail.com>
Details
Message ID
<CAJPc2ZyLY+s6y9X=vSn-qG9qLaxkbaoej6dqYF1RBsr2GKqbzA@mail.gmail.com>
DKIM signature
pass
Download raw message
Hi,

It seems like whenever (seemingly randomly) I try to close a DM buffer
in a buffer created by wee_most, weechat SIGSEGV.
I have describe the problem, and provided stacktrace and crash dump
file in https://github.com/weechat/scripts/issues/548
Could you perhaps have a look at it?

Regards,
Per-Arne
Details
Message ID
<CYGE5SM3K79O.1AL17BWXUP2Z4@tardypad.me>
In-Reply-To
<CAJPc2ZyLY+s6y9X=vSn-qG9qLaxkbaoej6dqYF1RBsr2GKqbzA@mail.gmail.com> (view parent)
DKIM signature
pass
Download raw message
Hi Per-Arne,

> It seems like whenever (seemingly randomly) I try to close a DM buffer
> in a buffer created by wee_most, weechat SIGSEGV.
> I have describe the problem, and provided stacktrace and crash dump
> file in https://github.com/weechat/scripts/issues/548
> Could you perhaps have a look at it?

Thank for reaching out but unfortunately I'm not going to be able to 
help fix this issue.

I was developing wee-most solely for my usage of Mattermost at my 
previous job. And my current company is using Slack instead, which means 
that, for now, I'm back to using wee-slack.

I don't have the time nor the motivation to continue working on wee-most 
without having any use of it myself. I'm still willing to help with 
answering basic questions and merging simple patches though.

I was not used to close DM buffers so that's probably why I've never 
encountered that bug. I don't expect it to be too hard to figure out. 
Hopefully someone can send a patch for it. 

Regards,

--
Damien
Reply to thread Export thread (mbox)