search for: mnums

Hi All, Found an issue with DUNDILOOKUP function in Asterisk 1.6.0.5. I was using DUNDIQUERY (Set(ID=${DUNDIQUERY(${MNUM},priv,b)})) for dundilookup and it was working fine. But when I tried to use DUNDILOOKUP function (Set(DL=${DUNDILOOKUP(${MNUM},priv,b)})), it didn't retuen me a result. Moreover, the cli command 'dundi lookup 12345 at priv' returned me the result at the same time!

...imenoBMTxpa.c:226:5: warning: incompatible implicit declaration of built-in function ‘exit’ [enabled by default] exit(6); ^ himenoBMTxpa.c: In function ‘newMat’: himenoBMTxpa.c:239:5: warning: incompatible implicit declaration of built-in function ‘malloc’ [enabled by default] malloc(mnums * mrows * mcols * mdeps * sizeof(float)); ^ himenoBMTxpa.c: In function ‘clearMat’: himenoBMTxpa.c:248:5: warning: incompatible implicit declaration of built-in function ‘free’ [enabled by default] free(Mat->m); ^ '-cmpxchg16b' is not a recognized feature for this target (...

...ing: incompatible implicit declaration of built-in function ‘exit’ [enabled by default] > exit(6); > ^ > himenoBMTxpa.c: In function ‘newMat’: > himenoBMTxpa.c:239:5: warning: incompatible implicit declaration of built-in function ‘malloc’ [enabled by default] > malloc(mnums * mrows * mcols * mdeps * sizeof(float)); > ^ > himenoBMTxpa.c: In function ‘clearMat’: > himenoBMTxpa.c:248:5: warning: incompatible implicit declaration of built-in function ‘free’ [enabled by default] > free(Mat->m); > ^ > '-cmpxchg16b' is not a recogn...

Unfortunately there's no sure-fire way to distinguish a sched "op" from regular ones. They happen purely based on position. So for disassembly, use the byte position in the file to determine whether the current op should be decoded as sched or as regular. For assembly, we go back to using a shared table. Ideally we would pick out which one to use based on the position in the