| 05:00.23 | *** join/#asterisk-bugs tzafrir_laptop (~tzafrir@212.179.75.202) |
| 08:46.09 | *** join/#asterisk-bugs 17WAAVXSG (~nobody@nat/digium/session) |
| 08:46.15 | *** join/#asterisk-bugs 17WAAVXSG (~nobody@nat/digium/x-pmhwfcizvfdexahu) |
| 12:35.28 | *** join/#asterisk-bugs zerohalo (~zerohalo@74.61.196.236) |
| 13:51.50 | *** join/#asterisk-bugs tzafrir_laptop (~tzafrir@212.179.75.202) |
| 14:00.43 | *** join/#asterisk-bugs leifmadsen (~Leif@asterisk/documenteur-extraordinaire/blitzrage) |
| 14:00.43 | *** mode/#asterisk-bugs [+o leifmadsen] by ChanServ |
| 14:12.05 | *** join/#asterisk-bugs mjordan (~mjordan@nat/digium/x-poqdljmmxuslexyc) |
| 14:12.06 | *** mode/#asterisk-bugs [+o mjordan] by ChanServ |
| 15:04.20 | *** join/#asterisk-bugs putnopvut (~putnopvut@asterisk/master-of-queues/mmichelson) |
| 15:04.20 | *** mode/#asterisk-bugs [+o putnopvut] by ChanServ |
| 15:22.55 | *** join/#asterisk-bugs Jamuel (~Adium@cpe-107-8-85-132.columbus.res.rr.com) |
| 15:23.32 | Jamuel | Hi. |
| 15:25.14 | Jamuel | I'm seeing segfaults in 1.8.20.0 rc1 which I believe are related to ASTERISK-20032. Should I open a new ticket or can the previous be reopened as a regression? I've got a good BT and it seems fairly repeatable. |
| 15:30.12 | mjordan | that issue is still open - you can attach the bt to that issue |
| 15:36.15 | Jamuel | okay—I thought it was closed since it was listed in the ChangeLog for 1.8.19 |
| 15:41.10 | mjordan | no. The patch that was committed was simply a method of reducing the error messages by reporting the error condition up the chain. You can still have a timer related failure, which is the root problem people are seeing on that issue. |
| 15:45.23 | Jamuel | ahh—okay. |
| 15:53.10 | Jamuel | thanks—Matt. BT attached to the issue. |
| 15:59.36 | mjordan | got it, taking a look now. Thanks for uploading it :-) |
| 16:05.32 | *** join/#asterisk-bugs elguero_ (04353e8a@gateway/web/freenode/ip.4.53.62.138) |
| 16:44.21 | Jamuel | NP |
| 16:53.28 | mjordan | hm. That's pretty odd. Do you have any errors in the log file leading up to the crash, specifically any indicating that the timer failed to acknowlege? |
| 17:01.41 | Jamuel | let me check |
| 17:04.01 | mjordan | commenting on the issue as well; probably better to have the conversation there so it's recorded |
| 17:05.40 | Jamuel | ok |
| 17:08.12 | Jamuel | Matt: nothing remarkable in the log but I was only running Verbose=3 Debug = 0; is it worth trying again with both at 10? |
| 17:08.27 | mjordan | nah, it should be an error |
| 17:08.55 | mjordan | I'm not seeing how we could get into a state where a fax session started and there's no timer at all. I'll try to put together a patch to debug it, but that just seems very odd |
| 17:10.33 | Jamuel | ok |
| 21:22.35 | *** part/#asterisk-bugs mjordan (~mjordan@nat/digium/x-poqdljmmxuslexyc) |