| 01:14.03 | *** join/#asterisk-dev leedm777 (~textual@173-16-52-28.client.mchsi.com) |
| 01:14.03 | *** mode/#asterisk-dev [+o leedm777] by ChanServ |
| 01:18.12 | tuxd00d | Would it be benefical to submit a core from a crash of 13.13-cert4? |
| 01:34.40 | rmudgett | Core files are only valid on the machine that created them. Also certified asterisk is only supported if you have a SLA with Digium. https://www.digium.com/products/asterisk/certified-asterisk has a FAQ about certified asterisk. |
| 01:52.11 | tuxd00d | Iâm sorry, I meant the backtrace produced by ast_coredumper |
| 01:55.17 | tuxd00d | And I wasnât looking for support. I was just wondering if it would be beneficail to provide it. |
| 01:56.39 | gtjoseph | sure it would |
| 01:56.57 | gtjoseph | especially if it's something that can be reproduced |
| 01:57.00 | tuxd00d | Jire doesnât have a version option for cert |
| 01:57.24 | tuxd00d | It crashes once or twice a day⦠with no call load. |
| 01:57.41 | tuxd00d | A half dozen PJSIP endpoints but not dialplan yet. |
| 01:58.01 | gtjoseph | you can to 13.13 |
| 01:58.23 | gtjoseph | was asterisk compiled with DONT_OPTIMIZE and BETTER_BACKTRACES? |
| 02:01.34 | tuxd00d | Yep and Yep |
| 02:02.16 | tuxd00d | 13.13.0 or 13.13.1? |
| 02:05.01 | tuxd00d | I didnât capture a thread lock, but that is only needed on deadlocks, correct? Asterisk doesnât automatically restart on a deadlock, correct? |
| 02:16.20 | *** join/#asterisk-dev leedm777 (~textual@2604:2d80:8404:8011:3ce1:69a8:7c69:5c4f) |
| 02:16.21 | *** mode/#asterisk-dev [+o leedm777] by ChanServ |
| 02:49.34 | gtjoseph | tuxd00d: deadlock debugging is very intensive, you need DEBUG_THREADS. You CAN set DETECT_DEADLOCKS but again, it's very intensive. |
| 03:39.25 | *** join/#asterisk-dev leedm777 (~textual@2604:2d80:8404:8011:19d:e080:add0:3e80) |
| 03:39.26 | *** mode/#asterisk-dev [+o leedm777] by ChanServ |
| 03:56.26 | tuxd00d | I can enable the thread debugging, if someone says it is needed on https://issues.asterisk.org/jira/browse/ASTERISK-27227 . I can keep this system unused for a while. |
| 04:25.20 | *** join/#asterisk-dev snuff-work (~snuff-wor@210.9.148.102) |
| 04:25.20 | *** mode/#asterisk-dev [+o snuff-work] by ChanServ |
| 06:04.10 | *** part/#asterisk-dev pnlarsson (~niklas@2a02:760:1000:e:48ac:e5b7:5663:136d) |
| 06:15.16 | *** join/#asterisk-dev jkroon (~jkroon@165.16.204.43) |
| 06:39.02 | *** join/#asterisk-dev CELYA_ (~Thunderbi@LStLambert-657-1-90-73.w80-13.abo.wanadoo.fr) |
| 06:44.05 | *** join/#asterisk-dev tsearle (~tsearle@37.19.10.33) |
| 06:44.05 | *** mode/#asterisk-dev [+o tsearle] by ChanServ |
| 06:53.33 | *** join/#asterisk-dev tsearle (~tsearle@37.19.10.33) |
| 06:53.33 | *** mode/#asterisk-dev [+o tsearle] by ChanServ |
| 07:03.13 | *** join/#asterisk-dev hehol (~hehol@gatekeeper.loca.net) |
| 07:16.39 | *** join/#asterisk-dev pchero (~pchero@109.70.54.56) |
| 08:22.37 | *** join/#asterisk-dev pnlarsson (~niklas@2a02:760:1000:e:48ac:e5b7:5663:136d) |
| 09:01.52 | *** join/#asterisk-dev jkroon (~jkroon@165.16.204.43) |
| 10:52.09 | *** join/#asterisk-dev CELYA_ (~Thunderbi@LStLambert-657-1-90-73.w80-13.abo.wanadoo.fr) |
| 11:02.47 | *** join/#asterisk-dev libardi (~libardi@179.159.11.133) |
| 13:13.33 | *** join/#asterisk-dev leedm777 (textual@nat/digium/x-unvwmtczbqcywglp) |
| 13:13.33 | *** mode/#asterisk-dev [+o leedm777] by ChanServ |
| 13:46.01 | *** join/#asterisk-dev cresl1n (Adium@asterisk/libpri-and-libss7-expert/Cresl1n) |
| 13:46.01 | *** mode/#asterisk-dev [+o cresl1n] by ChanServ |
| 13:53.41 | *** join/#asterisk-dev bford (d8cff501@gateway/web/freenode/ip.216.207.245.1) |
| 13:53.41 | *** mode/#asterisk-dev [+o bford] by ChanServ |
| 14:18.20 | *** join/#asterisk-dev kharwell (kharwell@nat/digium/x-nmptjrgjktfjxroc) |
| 14:18.20 | *** mode/#asterisk-dev [+o kharwell] by ChanServ |
| 14:58.57 | *** join/#asterisk-dev leedm777 (textual@nat/digium/x-fcbgvftzygvhcwzu) |
| 14:58.57 | *** mode/#asterisk-dev [+o leedm777] by ChanServ |
| 15:29.14 | *** join/#asterisk-dev kannan (~chatzilla@182.65.34.205) |
| 15:31.18 | *** part/#asterisk-dev pnlarsson (~niklas@2a02:760:1000:e:48ac:e5b7:5663:136d) |
| 15:44.25 | *** join/#asterisk-dev leedm777 (textual@nat/digium/x-gqnyhhhhmoksbhar) |
| 15:44.25 | *** mode/#asterisk-dev [+o leedm777] by ChanServ |
| 16:05.12 | *** join/#asterisk-dev CELYA_ (~Thunderbi@LStLambert-657-1-90-73.w80-13.abo.wanadoo.fr) |
| 17:11.54 | kannan | hi. from https://wiki.asterisk.org/wiki/display/AST/Asterisk+Security+Event+Logger - " The content of the log file is well defined and is in an easily interpretable format allowing for external scripts to read and act upon." . Does this mean that one can safely open the file with an IO handle separately? Can such an external script also do concurrent writes ? |
| 17:12.26 | file | er, it's not made for you to write to it yourself really... |
| 17:14.04 | kannan | file : thanks, thats what i thought, heh. |
| 17:55.44 | *** join/#asterisk-dev tzafrir (~tzafrir@bzq-179-40-170.cust.bezeqint.net) |
| 17:55.44 | *** mode/#asterisk-dev [+o tzafrir] by ChanServ |
| 17:56.31 | *** join/#asterisk-dev CELYA_ (~Thunderbi@2a01cb0583d31d009593eb2aa7a55780.ipv6.abo.wanadoo.fr) |
| 19:00.05 | *** join/#asterisk-dev leedm777 (textual@nat/digium/x-zoivggibdgrsuitt) |
| 19:00.05 | *** mode/#asterisk-dev [+o leedm777] by ChanServ |
| 19:01.53 | *** join/#asterisk-dev dustinm (~dustinm@68.ip-149-56-14.net) |
| 20:22.31 | *** join/#asterisk-dev jkroon (~jkroon@165.16.204.166) |
| 21:03.23 | *** join/#asterisk-dev tuxd00d_ (~tuxd00d@ip68-106-11-138.ph.ph.cox.net) |
| 21:18.14 | *** join/#asterisk-dev leedm777 (~textual@2604:2d80:8404:8011:85fe:bb21:245f:f38d) |
| 21:18.14 | *** mode/#asterisk-dev [+o leedm777] by ChanServ |
| 21:43.25 | seanbright | * \warning Do not use this function unless you really know what you are doing. |
| 21:43.29 | seanbright | * And "I want the port number" is not knowing what you are doing. |
| 21:43.37 | seanbright | this has to be one of the more useless comments i have ever read |
| 21:46.01 | file | seanbright: are you doing... nevermind |
| 21:46.07 | seanbright | i am |
| 21:46.14 | seanbright | someone has to |
| 21:46.28 | file | says you |
| 21:46.56 | seanbright | file: any idea what that comment means? |
| 21:47.00 | file | no |
| 21:47.03 | file | I never have |
| 21:47.03 | seanbright | ast_sockaddr_port() is used a lot |
| 21:47.37 | file | yeah, I've never understood why and the comment doesn't say really so I ignored it |
| 21:47.39 | file | and it's been fine |
| 21:49.23 | seanbright | and i'm correct that you can't call ast_sockaddr_stringify twice "at the same time" correct? |
| 21:49.37 | seanbright | or is that no longer true? |
| 21:49.54 | file | you are correct |
| 21:50.11 | seanbright | ah. TLS. yes. |
| 21:50.14 | seanbright | kk |
| 21:50.29 | file | TLS, it's good and it's bad |
| 21:51.05 | seanbright | actually... explain to me why that is bad? |
| 21:51.08 | seanbright | oh |
| 21:51.11 | seanbright | it returns the same pointer |
| 21:51.12 | seanbright | got it |
| 21:51.14 | file | yes |
| 21:51.51 | file | it uses the same buffer space, so it's convenient but if you need it multiple times then you need to copy the result |
| 21:52.25 | seanbright | righto |
| 22:58.53 | *** join/#asterisk-dev jkroon (~jkroon@165.16.204.166) |
| 23:14.37 | *** part/#asterisk-dev kharwell (kharwell@nat/digium/x-nmptjrgjktfjxroc) |