| 02:25.40 | *** join/#asterisk-bugs leifmadsen (n=Leif@asterisk/documenteur-extraordinaire/blitzrage) |
| 02:25.40 | *** mode/#asterisk-bugs [+o leifmadsen] by ChanServ |
| 07:04.17 | *** join/#asterisk-bugs |Cybex| (n=John@atwork-20.r-212.178.82.atwork.nl) |
| 08:06.06 | *** join/#asterisk-bugs mpe (n=mpe@gate.ipvision.dk) |
| 10:59.13 | *** join/#asterisk-bugs caio1982 (i=caio1982@CAcert-br/caio1982) |
| 13:31.53 | *** join/#asterisk-bugs TheDavidFactor (n=chatzill@fw1.safedataisp.net) |
| 14:10.10 | *** join/#asterisk-bugs davidbrillert (n=aragon12@216.235.8.130) |
| 14:34.43 | *** join/#asterisk-bugs putnopvut (n=putnopvu@asterisk/master-of-queues/mmichelson) |
| 14:34.43 | *** mode/#asterisk-bugs [+o putnopvut] by ChanServ |
| 15:15.22 | *** part/#asterisk-bugs |Cybex| (n=John@atwork-20.r-212.178.82.atwork.nl) |
| 15:35.22 | *** join/#asterisk-bugs Deeewayne (n=dwayne@75.76.254.162) |
| 15:35.22 | *** mode/#asterisk-bugs [+o Deeewayne] by ChanServ |
| 15:46.33 | *** join/#asterisk-bugs caio1982_ (i=caio1982@CAcert-br/caio1982) |
| 15:55.05 | *** join/#asterisk-bugs jpeeler (n=jpeeler@asterisk/digium-software-dev/jpeeler) |
| 16:19.46 | *** join/#asterisk-bugs Corydon76-lap (n=Corydon7@nat/digium/x-tgyidnroowhxaiaf) |
| 16:19.46 | *** mode/#asterisk-bugs [+o Corydon76-lap] by ChanServ |
| 16:42.27 | *** join/#asterisk-bugs caio1982 (i=caio1982@CAcert-br/caio1982) |
| 17:22.35 | *** join/#asterisk-bugs ebroad (n=EB@72.11.213.195) |
| 21:16.45 | *** join/#asterisk-bugs putnopvut (n=putnopvu@asterisk/master-of-queues/mmichelson) |
| 21:16.46 | *** mode/#asterisk-bugs [+o putnopvut] by ChanServ |
| 22:06.18 | *** join/#asterisk-bugs Whtsup (n=sssi@WimaxUser372-235.wateen.net) |
| 22:06.35 | *** part/#asterisk-bugs Whtsup (n=sssi@WimaxUser372-235.wateen.net) |
| 22:29.25 | *** join/#asterisk-bugs Micc (n=Micc@c-98-225-57-96.hsd1.wa.comcast.net) |
| 22:31.01 | Micc | 1.6.1.10 seems to be running great so far. |
| 22:31.33 | Micc | I'm hoping it solves my mutex crash problem. I read all the fixes and a few of them seem like they could be related. |
| 22:32.20 | Micc | Is it common that a single bug causes multiple problems and crashes in different ways? |
| 22:34.04 | putnopvut | Micc: it's certainly possible. |
| 22:34.37 | putnopvut | Say that there is some sort of memory corruption issue. It may be that different areas of code access the invalid memory, and so sometimes the crash happens in a different part of the code. |
| 22:36.05 | Micc | yeah, I know thats possible. This seemed like a timing issue. |
| 22:36.21 | Micc | crashed in pthread_mutex_lock and unlock |
| 22:37.55 | putnopvut | Probably because the structure in which the lock was located had been freed or some such. |
| 22:45.31 | Corydon76-lap | Those are the best bugs |
| 22:58.26 | Micc | I think it was related to hangup being called twice. |
| 22:58.47 | Micc | so it may have freed the lock structure before the other call finished. |