| 01:58.28 | *** join/#asterisk-dev sahmed (~sahmed@cpe-70-114-236-63.austin.res.rr.com) |
| 05:23.54 | *** join/#asterisk-dev coreyfarrell (~coreyfarr@68-114-57-249.dhcp.davl.vt.charter.com) |
| 05:23.54 | *** mode/#asterisk-dev [+o coreyfarrell] by ChanServ |
| 07:17.19 | *** join/#asterisk-dev CELYA_ (~Thunderbi@2a01:e0a:d:1111:b749:768d:ed77:7c9a) |
| 07:47.35 | *** join/#asterisk-dev pchero_work (~pchero@87.213.247.82) |
| 09:10.32 | *** join/#asterisk-dev snuff-work (~snuff-wor@202-161-112-134.tpgi.com.au) |
| 09:10.32 | *** mode/#asterisk-dev [+o snuff-work] by ChanServ |
| 09:33.24 | *** join/#asterisk-dev hehol (~hehol@gatekeeper.loca.net) |
| 09:39.00 | *** join/#asterisk-dev jkroon (~jkroon@165.16.203.126) |
| 11:25.29 | *** join/#asterisk-dev s3c70r (~user@uranus.belnet.de) |
| 11:25.45 | s3c70r | hi |
| 11:31.46 | s3c70r | Could you help me out with some lines in source code? :) |
| 11:34.20 | file | if you ask a question someone may answer |
| 11:40.09 | s3c70r | Right now i try to debug a segfault for asterisk 13.21. Maybe you could help me out somehow to give me some clues which conditions could had lead to the crash so i could find and maybe report the problem to you. |
| 11:41.16 | s3c70r | The main problem is that at some certain point in execution under heavy load tsx->transport in sip_transaction.c:1881 is NULL pointer which lead to the segfault. |
| 11:47.05 | s3c70r | the last functions on stack which was called was pj_mutex_unlock <- pj_atomic_dec_and_get <- pjsip_transport_dec_ref and before that the ioqueue key hold an READABLE_EVENT (very outer-most frame) |
| 11:47.36 | s3c70r | i could send you the actual BT if needed |
| 11:48.46 | file | personally I'm not a fan of chasing problems from old versions, and to file an issue we'd require reproduction with current Asterisk and PJSIP |
| 11:49.44 | file | someone else may help out |
| 11:50.21 | s3c70r | I can totally understand that and i dont like it either but i am sitting on the last "stable" certified version of asterisk which seams to be the newest certified version available |
| 11:51.01 | file | if you have a support agreement then you should contact Sangoma Technical Support, otherwise you have to find someone to help you, further investigate yourself, or upgrade |
| 11:55.07 | s3c70r | Basically i will have to stick to further investigation myself than. It would be much more pleasant to debug this nasty problem with someone else's help too :] |
| 11:56.31 | s3c70r | The main idea would be to find out what was the cause of the cause of the NULL pointer and maybe transfer the reproduction to newer versions to find out if it is still a problem |
| 12:03.49 | *** join/#asterisk-dev pchero_work (~pchero@51.247.195.35.bc.googleusercontent.com) |
| 12:10.39 | s3c70r | If that's OK i would conclude my problem and send it to the dev mailing list. Maybe someone will join in later |
| 12:34.50 | *** join/#asterisk-dev pc-m (~pcm@ipagstaticip-cf899324-841a-2614-948a-7dbf21746b29.sdsl.bell.ca) |
| 12:39.29 | *** join/#asterisk-dev pchero_work (~pchero@87.213.247.82) |
| 12:41.09 | *** join/#asterisk-dev pchero_work (~pchero@87.213.247.82) |
| 13:00.49 | *** join/#asterisk-dev pchero_work (~pchero@87.213.247.82) |
| 13:25.44 | *** join/#asterisk-dev rmudgett (rmudgett@nat/digium/x-iwfmhewznhxpjnel) |
| 13:39.35 | *** join/#asterisk-dev sduthil (~sduthil@ipagstaticip-cf899324-841a-2614-948a-7dbf21746b29.sdsl.bell.ca) |
| 13:46.37 | *** join/#asterisk-dev sahmed (~sahmed@cpe-70-114-236-63.austin.res.rr.com) |
| 15:08.13 | *** join/#asterisk-dev pc-m (~pcm@cable-66-129-132-216.b2b2c.ca) |
| 15:16.27 | *** join/#asterisk-dev kharwell (uid358942@gateway/web/irccloud.com/x-boebvarqpgbwsors) |
| 15:16.27 | *** mode/#asterisk-dev [+o kharwell] by ChanServ |
| 15:32.52 | *** join/#asterisk-dev bford (uid283514@gateway/web/irccloud.com/x-klisavkzfeismobq) |
| 15:32.52 | *** mode/#asterisk-dev [+o bford] by ChanServ |
| 16:55.48 | *** join/#asterisk-dev jkroon (~jkroon@165.16.204.110) |
| 17:01.28 | coreyfarrell | asterisk-bugs mailing list allows people to directly post |
| 17:33.44 | *** join/#asterisk-dev rmudgett (rmudgett@nat/digium/x-skgrbzlkhfwxpxbs) |
| 17:33.44 | *** mode/#asterisk-dev [+o rmudgett] by ChanServ |
| 17:44.01 | *** join/#asterisk-dev CELYA_ (~Thunderbi@2a01cb0583d31d00f4d7ddd1bc0987bc.ipv6.abo.wanadoo.fr) |
| 17:58.08 | kharwell | I'm assuming that shouldn't be the case? |
| 17:58.21 | seanbright | i've opened a internal ticket with IT |
| 17:58.24 | file | I think back in the day it was used to discuss some issues here and there |
| 17:58.45 | seanbright | they'll get to it after they make the release scripts public... |
| 17:58.53 | seanbright | *cough* |
| 17:59.13 | file | so much stuff, so little time |
| 17:59.39 | seanbright | so true |
| 17:59.50 | seanbright | that could literally take minutes |
| 17:59.55 | seanbright | no one has that kind of bandwidth |
| 18:00.08 | seanbright | temporarily stops trolling |
| 18:02.11 | file | it's not that easy |
| 18:02.12 | seanbright | well yeah |
| 18:08.42 | *** join/#asterisk-dev pc-m (~pcm@cable-66-129-132-216.b2b2c.ca) |
| 20:15.49 | *** join/#asterisk-dev pchero_work (~pchero@dhcp-077-249-058-090.chello.nl) |
| 20:54.56 | kharwell | we usually require tests for new features going into base branches, but not sure if we're setup for one to be written for this patch? https://gerrit.asterisk.org/c/asterisk/+/13166 |
| 20:55.51 | file | not really methinks |
| 20:55.53 | kharwell | anyone know of a way to test that with the testsuite? Setup two asterisk instances. one acting as the http server? Or too much trouble |
| 20:56.41 | kharwell | alright prob fine to do without then. At least is an optional feature being added |
| 21:20.55 | *** join/#asterisk-dev CELYA_1 (~Thunderbi@anantes-655-1-124-21.w90-59.abo.wanadoo.fr) |
| 21:54.56 | kharwell | hrm didn't we fix this? https://jenkins2.asterisk.org/job/asterisk-gatetests/job/certified%252F16.3/35/artifact/tests/CI/output/ari1/logs/rest_api/CORS/backtrace_6622.txt |
| 21:55.06 | kharwell | seemingly |
| 21:55.40 | gtjoseph | hmmm. doesn't ring a bell but that doesn't mena much |
| 21:57.15 | file | I vaguely remember it, but do remember that's certified 16.3 |
| 21:58.20 | kharwell | aah true didn't notice it was the cert branch |
| 21:59.22 | kharwell | also it might have been this I was thinking of: https://issues.asterisk.org/jira/browse/ASTERISK-28585 |
| 21:59.42 | kharwell | I'll leave it for now since cert. If it pops up in a non cert someone can open an issue |