[Asterisk-Dev] Re: is this a bug?

[Brian West]

Ok I have tried over and over and over to get a segfault doing ctrl-c...
during a call, during a reload just about any way shape or form I can think.

IT DOES NOT HAPPEN ON MY BOX.

*CLI> set verbose 10
Verbosity was 0 and is now 10
*CLI>     -- Executing Answer("SIP/16-3611", "") in new stack
    -- Executing MusicOnHold("SIP/16-3611", "default") in new stack
    -- Started music on hold, class 'default', on SIP/16-3611
    -- Stopped music on hold on SIP/16-3611
  == Spawn extension (default, 999, 2) exited non-zero on 'SIP/16-3611'
Beginning asterisk shutdown....
Beginning asterisk shutdown....
Executing last minute cleanups
  == Destroying musiconhold processes
Asterisk cleanly ending (2).
Killed

This is with mgp123 running too... So I put it to you like this.  You must
have something locally WRONG with your system or libs because I can tell I
have seen it happen before in the past but not in many months.

Can you provide a bit of info about your linux distro?  I have an idea of
what might be causing it... but I'm waiting on a compile to finish.

bkw


> -----Original Message-----
> From: asterisk-dev-bounces at lists.digium.com [mailto:asterisk-dev-
> bounces at lists.digium.com] On Behalf Of Andrew Kohlsmith
> Sent: Tuesday, January 25, 2005 6:12 PM
> To: Asterisk Developers Mailing List
> Subject: Re: [Asterisk-Dev] Re: is this a bug?
> 
> On January 25, 2005 06:00 pm, Edwin Groothuis wrote:
> > It will still abort when somebody accidently presses ^C to get out
> > of screen. Don't say it won't happen, has happened twice here in
> > the last three months.
> 
> No I didn't say it wouldn't happen, I know it does.  I am saying that
> Tilghman's attutude of "you know not what you're doing because you run
> asterisk in an xterm so quit bitching about ^C" is wrong - Aside from
> confusing -c with colour (yes this is embarassing) I *do* know what I'm
> doing, I've been running asterisk for over a year now and put over 20k
> minutes a month through my servers.
> 
> ^C is being trapped and is exiting gracefully most of the time.  The OP
> did
> not have that though, the OP had a segfault and a crash on ^C.  That's a
> bug.
> 
> -A.
> _______________________________________________
> Asterisk-Dev mailing list
> Asterisk-Dev at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-dev
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev