[Asterisk-Dev] Internals of Asterisk

[Matt Fredrickson]

On Fri, Mar 18, 2005 at 11:49:53AM -0500, Steve Kann wrote:
> Kevin P. Fleming wrote:
> 
> >Mike M wrote:
> >
> >>Use the force, read the source.  It's a bromide that works. If you
> >>haven't already, pull the source down and speed read it. Sketch out how
> >>you think it works. Then get it running and use a debugger or
> >>(my favorite) printf/printk to trace operation.  Come back with specific
> >>questions.
> >
> >
> >Yeah, gdb and Asterisk is a fun combination... just when you think you 
> >know what's going on, some other thread changes what you are looking 
> >at :-)
> 
> 
> Speaking of this, it might be cool to take a look at google's 
> open-source "coredumper" library;  we could build asterisk with this, 
> and then have it dump a multi-threaded core on command (without 
> crashing), for inspection..

Have you tried using the gdb command 'gcore' (I think it is) before?  It
does that.

Matthew Fredrickson