[Asterisk-Users] Re: System call forked - more stuff

[Bill Michaelson]

It gets better (worse)...

I had been testing with console (-c) mode. When I allow * to run background,
it crashes after the system() call (which succeeds, by the way). The -vvv
option yields these final messages before *poof*...

 == Spawn extension
(intern-post, 112, 1) exited non-zero on 'SIP/248379-bcdc'
 -- Executing Macro("SIP/248379-bcdc", "record-cleanup") in new stack
 -- Executing SetVar("SIP/248379-bcdc", "MONITORDIR=/var/spool/asterisk/monitor")
in new stack
Feb 21 09:56:57 WARNING[1209214528]: ast_expr.y:346 ast_yyerror: ast_yyerror():
syntax error: parse error
 -- Executing GotoIf("SIP/248379-bcdc", "0?6:3") in new stack
 -- Goto (macro-record-cleanup,s,3)
 -- Executing System("SIP/248379-bcdc", "/usr/local/bin/wmix /var/spool/asterisk/monitor/20040221-095652-111-112-in.wav
/var/spool/asterisk/monitor/20040221-095652-111-112-out.wav  /var/spool/asterisk/monitor/20040221-095652-111-112")
in new stack

I don't know what the yyerror is about either.

Re: [Asterisk-Users] Re: System call forked - more stuff

[Tilghman Lesher]

On Saturday 21 February 2004 09:01, Bill Michaelson wrote:
 Feb 21 09:56:57 WARNING[1209214528]: ast_expr.y:346 ast_yyerror:
 ast_yyerror(): syntax error: parse error
 -- Executing GotoIf(SIP/248379-bcdc, 0?6:3) in new stack

 I don't know what the yyerror is about either.

Can't help you with the crash (unless you post a backtrace), but the
yyerror is specifically about a conditional that isn't parseable as
such.  The most common error is the use of a variable that has not
been defined, such as:

GotoIf(${FOO}?6:3) or
GotoIf($[${FOO} = 23]?6:3)

Note that if you use DBGet and retrieve a key which does not exist,
the variable isn't defined in that case, either.

-Tilghman

___
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users