On 24 August 2010 14:34, Steve Davies <davies...@gmail.com> wrote: > On 24 August 2010 08:07, Stefan Schmidt <s...@sil.at> wrote: >> Steve Davies schrieb: >>> On 23 August 2010 18:32, Stefan Schmidt <s...@sil.at> wrote: >>> >>>> hello, >>>> >>>> have you allready tried strace ? >>>> you could just easily start asterisk with this command: >>>> >>>> strace asterisk -vvvvdddd >>>> >>> >>> Yes, I tried this. Output just stops along with everything else and >>> there are no clues. >>> >> if you know in which function this happens you could also patch some >> ast_verbose rows into this function to see where it happens. >> >> another thing you could try is using gprof to see which functions waste >> much time. for this you need to compile asterisk like this: >> make ASTCFLAGS="-pg" ASTLDFLAGS="-pg" >> make install >> >> after this you will see a gmon.out file in the directory from where you >> have started asterisk (your home) and then you could use gprof with this >> gmon.out file. >> >> maybe you will find something with this. > > I found that doing a build with debug symbols included and running > under gdb slowed down asterisk enough for me to get debug output. > > Thanks for the pointers. I'll start a separate thread on working out > what the hell is going on :)
Turns out that 1.6.2.11 fixes the symptom, and the cause is in my own "hack" to the code. Holding locks too long == verybad. Steve -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
