search for: 24233

I have a server with an asterisk ss7 link connected to a Siemens working well for over a year. A few days ago I started having problems with signaling. I found the following logs in / var / log / messages Sep 12 11:49:25 call3 kernel: [1018427.030959] dahdi: Master changed to TE2/0/2 Sep 12 11:49:25 call3 kernel: [1018427.120740] dahdi: Master changed to TE2/0/1 Sep 12 11:49:26 call3 kernel:

LLVM3.8 version. https://bugs.llvm.org//show_bug.cgi?id=24233. The example can catch exception. But I use my own code for testing, CustomEHMemoryManager allocated memory address is very large, allocateCodeSection, allocateDataSection assigned address (more than 32 bit address space) is getting smaller and smaller. Cause registerEHFrames to fail. 3.9.1 or 4.0....

For help: Llvm generated instruction calls a function (extern), the function will have a SEH exception (EXCEPTION_ACCESS_VIOLATION), But JIT can not capture the exception of the EXCEPTION_ACCESS_VIOLATION. I saw Bug 24233. EXCEPTION_ACCESS_VIOLATION exception cannot be captured after modification. How to catch EXCEPTION_ACCESS_VIOLATION exceptions on win64 ? haifeng.qin at wellintech.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/...

...8765432112345678] MyJit.dll!MyCallingFunction() ... It looks like visual studio get lost while walking up stack. Does anyone know where it could come from ? I have disabled all optimisations (among them is the omit-frame-pointer). I have seen this bug here : https://bugs.llvm.org/show_bug.cgi?id=24233 which is quite similar but it is quite old now, and since the proposed patch has been posted, the code in RuntimeDyldCOFFX86_64.h has changed and it is difficult for me to know if it has really been fixed since or not. Could it be related to the way IR CreateAlloca are used to build local variable...

...ess willing or able to be given JIT-frame information from LLVM. (I assume somehow it can be done, for dotNET. I just don't know how.) On Sat, Feb 29, 2020 at 11:07 PM Reid Kleckner via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Yes, I think https://bugs.llvm.org/show_bug.cgi?id=24233 needs to be > implemented to fix this. > > The Windows x64 unwinder doesn't generally look at frame pointers. We > would need to register unwind info to make this work. What you see is > fairly typical of attempting to unwind the stack when unwind info is > missing. > >...

For JITs it would appear that there is a patch needed for some kind of relocations. https://llvm.org/bugs/show_bug.cgi?id=24233 Is the patch really needed? What does it do? I'm not an expert here so asking. On Sun, Jul 3, 2016 at 2:48 AM, David Majnemer via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > > On Sat, Jul 2, 2016 at 5:22 PM, Michael Lewis via llvm-dev > <llvm-dev at lists.llvm.org&gt...

This is https://bugs.llvm.org/show_bug.cgi?id=24233. I don't think there's been any movement on it for a while. I don't *think* it should be hard, but I've never really pushed on it. On Tue, Jan 2, 2018 at 3:57 PM, Jason via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Hi, I use LLVM MCJIT extensively and one of the sore...

Hi, I am wondering what the status of Clang++ and LLVM on the Windows platform ? When I last saw what the state was there was not proper linking and more recently heard that the Structured Exception Handling was not working. The status page seems somewhat out of date ? Many thanks in advance, Aaron

Hi, I use LLVM MCJIT extensively and one of the sore spots is debugging. We lose stack information if we crash during execution of one of our JIT functions. I spent some time to understand Windows x64 stack/exception handling and was able to hardcode support for a single JIT function and was able to maintain the call stack correctly. However it requires knowledge of the prolog of the function to

Hi all, I have the following code: [use llvm to generate ir_func() ] in side the ir_func() there's a call to a native cpp function that throws an exception. (Just imagine changing the fibonacci example and calling a native c++ func that throws inside the fibonacci body) I can't seem to catch "foreign" exception or any exception using the following pseudo code: try { // cast

http://bugs.freedesktop.org/show_bug.cgi?id=20857 Summary: Xorg hangs when starting with nouveau Product: xorg Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

...; produces the problem. I spent quite some time debugging this and the fact > that data is incomplete though it's in the right place feels similar to > what I experienced with exceptions on Win64 (which turned out to be missing > registration calls https://llvm.org/bugs/show_bug.cgi?id=24233). > > Will you be at the dev meeting? We could take a look at this in one of the > labs. > > Sooner or later I will make it to a Bay Area dev meeting, promise! > Unfortunately not in November as I will be at ADC in London. However, I > will try to reproduce the issue in a minim...

I recently upgraded from llvm 3.7.1 to a pre release of llvm (3.8.0rc2) in order to test some issues regarding bug 24233. After upgrading I starting to see heap corruption messages in vs 2015 sp1 when my program exits. "HEAP[ConsoleEngine.exe]: Invalid address specified to RtlValidateHeap( 0000000000290000, 0000000000318698 )" Initially I only got it in Release build. Debug build seems to be fine, but rece...

Hi, I apologize if I'm posting this to the wrong list; if this is the case, please let me know. For some time now, I've been trying to get SEH exception handling to work in LLVM MCJIT (x64). While reading up on LLVM 3.8, I decided to pick it up again, because a lot has changed which simplifies things greatly. As a toy project, I'm attempting to catch an exception that's thrown

Hi In my project I am still getting crashes on Windows - these seem to occur intermittently when there is a longjmp that crosses the boundary from C code over JITed code. I posted regarding this issue previously: http://lists.cs.uiuc.edu/pipermail/llvmdev/2015-April/084919.html I was wondering if the support for stack unwinding on Win64 is now improved in LLVM - and if there are any particular

How : <a href="/show/all">All</a> Could become : <a href="/show/all" title="Show All" >All</a> This is possible with the standdard link_to function ?

...eird that the same compiler works fine with 3.7.1 any ideas would be appreciated On Wed, Feb 24, 2016 at 9:10 AM, koffie drinker <gekkekoe at gmail.com> wrote: > > I recently upgraded from llvm 3.7.1 to a pre release of llvm (3.8.0rc2) in > order to test some issues regarding bug 24233. > After upgrading I starting to see heap corruption messages in vs 2015 sp1 > when my program exits. > "HEAP[ConsoleEngine.exe]: Invalid address specified to RtlValidateHeap( > 0000000000290000, 0000000000318698 )" > > Initially I only got it in Release build. Debug bui...

...3.7.1 > > any ideas would be appreciated > > > On Wed, Feb 24, 2016 at 9:10 AM, koffie drinker <gekkekoe at gmail.com> > wrote: > >> >> I recently upgraded from llvm 3.7.1 to a pre release of llvm (3.8.0rc2) >> in order to test some issues regarding bug 24233. >> After upgrading I starting to see heap corruption messages in vs 2015 sp1 >> when my program exits. >> "HEAP[ConsoleEngine.exe]: Invalid address specified to RtlValidateHeap( >> 0000000000290000, 0000000000318698 )" >> >> Initially I only got it in...

...ain; charset="utf-8" > > On Sun, Jul 3, 2016 at 2:17 PM, Hayden Livingston <halivingston at gmail.com> > wrote: > >> For JITs it would appear that there is a patch needed for some kind of >> relocations. >> >> https://llvm.org/bugs/show_bug.cgi?id=24233 >> >> Is the patch really needed? What does it do? I'm not an expert here so >> asking. >> > > > I'm not really interested in the JIT case as I said originally, so I can't > answer that question. > > > >> >> On Sun, Jul 3, 2016 at...

...be appreciated >> >> >> On Wed, Feb 24, 2016 at 9:10 AM, koffie drinker <gekkekoe at gmail.com> >> wrote: >> >>> >>> I recently upgraded from llvm 3.7.1 to a pre release of llvm (3.8.0rc2) >>> in order to test some issues regarding bug 24233. >>> After upgrading I starting to see heap corruption messages in vs 2015 >>> sp1 when my program exits. >>> "HEAP[ConsoleEngine.exe]: Invalid address specified to RtlValidateHeap( >>> 0000000000290000, 0000000000318698 )" >>> >>> Ini...