<SPAM>RE: [Asterisk-Dev] Asterisk and AMD64 - Crashes

[Jerris, Michael MI]

> Brian C. Fertig
> 
> Here's a thought..  Are you getting a CORE DUMP file?  Use 
> the -g feature.  
> It comes in handy every now and then.
> 

A more helpful response would be how to do this.  Information on this
can be found at:
http://cvsweb.digium.com/index.cgi/asterisk/doc/README.backtrace?rev=1.1
.  If you need additional help, please log on to irc on irc.freenode.net
and join #asterisk-bugs and ask if anyone can assist in building
asterisk non-optimized and creating a proper backtrace for a crash.



> 
> [mailto:asterisk-dev-bounces at lists.digium.com] On Behalf Of Joseph
> 
> On Mon, 2005-09-12 at 11:18 -0400, Paul wrote:
> > Joseph wrote:
> > 
> > >On Mon, 2005-09-12 at 14:23 +0000, Mark Dickie wrote:
> > >  
> > >
> > >>I have asterisk 1.0.9 here running on a dual opteron without any 
> > >>troubles.
> > >>Set verbose and debug to 20 and post your log.  Then I'll take a
> look
> > >>at it.
> > >>
> > >>    
> > >>
> > >
> > >How do I set debut to 20?
> > >
> > >I've compiled asterisk ver.1.0.8 and 1.0.9 on Gentoo without any 
> > >problems or error mesages.
> > >When I start Asterisk in command line:
> > >asterisk -vvvvvvvr   ; it starts OK
> > >
> > >As soon as I connect Sipura-3000  unit to it, the message appear:
> > >Disconnecting from Asterisk server
> > >Executing last minute cleanups.
> > >
> > >I've try to look in asterisk log, nothing there indicating any
> errors.
> > >When I try to restart asterisk again:
> > >/etc/init.d/asterisk restart
> > >start-stop-daemon; warning: failed to kill 6147: No such process
> > >
> > >So in order to restart it I have to "Zap" asterisk.  I 
> would seems to
> me
> > >connecting Sipura ATA kills Aserisk PID; but I don't now why.
> > >
> > >  
> > >
> > Does this spa3k config and * config work okay on an x86 
> system? Just 
> > asking because before assuming the problem is 
> AMD64-specific I would 
> > want to be sure I haven't overlooked anything basic. I have 
> seen * do 
> > some strange things when I didn't have it configured just right 
> > regardless of CPU choice.
> 
> Everything worked flawlessly on x86, all the SPA3K and 
> Sipura-2002 work without any problem on x86.  But whenever, I 
> try to connect them to Asterisk running on AMD64 it just 
> crashes without spilling any extra information. 
> I run command line with: asterisk -vvvvvvvvr
> 
> >From what I know Sipura units don't have any preferred 
> settings for x86
> or AMD64.  All the IP and registration are correct, but even 
> if the weren't correct all would happen the ATA wouldn't 
> register with Asterisk.  It shouldn't crash astersik server.
>