search for: incontext

...ces@lists.digium.com > [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of > Damon Estep > Sent: Tuesday, September 13, 2005 10:57 PM > To: Asterisk Users Mailing List - Non-Commercial Discussion > Subject: [Asterisk-Users] PRI zap channels not cleared when > no match incontext for dialed number on inbound call > > Could some out there with a PRI check and see if this problem > shows up on your system? > > The test is to dial a number routed to * via a PRI where > there is no match in the dial plan for the dialed number. > > Asterisk will reje...

...lvm 3.6.2 I created a bug for it: https://llvm.org/bugs/show_bug.cgi?id=24521 I'm building a app where multiple code gen can happen in parallel. The documentation state that I need to use separate context. Each thread has it's own context. When code generating a constant number I use the *InContext() calls to create the types. The assert fails since the optimizer replaces some numbers with a global type. The values are equal but the types are not. I did patch some calls to compare on getTypeID() but got another assert a couple of days later in another source file. I needed 3.7 because of the...

I have used libdispatch (on FreeBSD) from JIT'd code without any issues, so I think your bug is elsewhere. David On 30 Jan 2013, at 07:43, Rick Mann wrote: > My host app calls runFunction() on my JITed code. It, in turn, calls a C function ("decode()") in the host app that then calls dispatch_async(). The runFunction() call returns as expected, but the block passed to

My host app calls runFunction() on my JITed code. It, in turn, calls a C function ("decode()") in the host app that then calls dispatch_async(). The runFunction() call returns as expected, but the block passed to dispatch_async() never gets called. The async block is supposed to call a function pointer callback that was passed in to decode(). Everything is being called on the main

...ounces@lists.digium.com [mailto:asterisk-users- > bounces@lists.digium.com] On Behalf Of Alexander Lopez > Sent: Tuesday, September 13, 2005 9:27 PM > To: Asterisk Users Mailing List - Non-Commercial Discussion > Subject: RE: [Asterisk-Users] PRI zap channels not cleared > whennomatchincontext for dialed number on inbound call > > > Yeah the "variable stays there" because the channel is never up to be > cleared. If you do something like > > exten => _X.,1,Wait(1) > exten => _X.,2,Hangup > > You will see the same behavior. Can you confirm??...

...nces@lists.digium.com [mailto:asterisk-users- > bounces@lists.digium.com] On Behalf Of Alexander Lopez > Sent: Tuesday, September 13, 2005 9:08 PM > To: Asterisk Users Mailing List - Non-Commercial Discussion > Subject: RE: [Asterisk-Users] PRI zap channels not cleared when no > matchincontext for dialed number on inbound call > > > I se what you are talking about I an able to reproduce!!! > > However your PRI may be in a Round-Robin picking order, that would cycle > through all of the channels until it reaches an end and then it repeats. > I set our PRI to first...

...s@lists.digium.com > [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of > Damon Estep > Sent: Tuesday, September 13, 2005 11:11 PM > To: Asterisk Users Mailing List - Non-Commercial Discussion > Subject: RE: [Asterisk-Users] PRI zap channels not cleared > when nomatchincontext for dialed number on inbound call > > But it does indicated that a variable is staying assigned > that should not be, which could have other impact over time??? > > The behavior is very different for c call where there is a > dialplan match for the dialed number, when the call...