search for: longjump

...ny bells (except below), I > can't guess from this what is the underlying cause of the problem. > There may be something wrong in how we use setjmp/longjmp or how > setjmp/longjmp works on Windows. > > It reminds me of a problem I've been debugging few days ago, when > longjump implementation segfaults on Windows 10 (recent but not > Insider build) probably soon after unwinding the stack, but only with > GCC 10 / MinGW 7 and only in one of the no-segfault tests, and only > with -03 (not -O2, not with with -O3 -fno-split-loops). The problem > was sensitive...

...and pushed out a > > syslinux-6.04-pre2 release, however, due to the issues with continuing > > to keep the main archive on kernel.org, I have moved the release archive to: > > Please add a non ancient gnu-efi snapshot too. > > Jocke You vill need two commits( Update the longjump calls to fit the new declaration, The VPrint definition is now part of the exports of gnu-efi) from https://github.com/joakim-tjernlund/syslinux/commits/master to build against a modern gnu-efi Jocke

...#39;t guess from this what is the underlying cause of the problem. >>> There may be something wrong in how we use setjmp/longjmp or how >>> setjmp/longjmp works on Windows. >>> >>> It reminds me of a problem I've been debugging few days ago, when >>> longjump implementation segfaults on Windows 10 (recent but not >>> Insider build) probably soon after unwinding the stack, but only with >>> GCC 10 / MinGW 7 and only in one of the no-segfault tests, and only >>> with -03 (not -O2, not with with -O3 -fno-split-loops). The problem...

...cause of the problem. > >>>> There may be something wrong in how we use setjmp/longjmp or how > >>>> setjmp/longjmp works on Windows. > >>>> > >>>> It reminds me of a problem I've been debugging few days ago, when > >>>> longjump implementation segfaults on Windows 10 (recent but not > >>>> Insider build) probably soon after unwinding the stack, but only with > >>>> GCC 10 / MinGW 7 and only in one of the no-segfault tests, and only > >>>> with -03 (not -O2, not with with -O3 -fn...

On Sat, Aug 22, 2020 at 8:39 AM Tomas Kalibera <tomas.kalibera at gmail.com> wrote: > > On 8/21/20 11:45 PM, m19tdn+9alxwj7d2bmk--- via R-devel wrote: > > Ah yes, this is related. I reported v2010 below, but it looks like I was updated to this Insider Build overnight without my knowledge, and conflated it with the new installation R v4 this morning. > > > > I will

...ongjmp for our exception handling on all platforms in > our regular (non-LLVM) code generators. I'd like to use the same > infrastructure with the LLVM code generator for code interoperability > purposes (the LLVM SjLj personality is not binary-compatible with our > existing setjump/longjump buffers). I'm moderately sure that SjLj presonality does not use system longjmp and does not claim to be binary compatible either. It usees the intrinsics. Joerg

...tunately that does not ring any bells (except below), I can't guess from this what is the underlying cause of the problem. There may be something wrong in how we use setjmp/longjmp or how setjmp/longjmp works on Windows. It reminds me of a problem I've been debugging few days ago, when longjump implementation segfaults on Windows 10 (recent but not Insider build) probably soon after unwinding the stack, but only with GCC 10 / MinGW 7 and only in one of the no-segfault tests, and only with -03 (not -O2, not with with -O3 -fno-split-loops). The problem was sensitive to these optimizatio...

...> > can't guess from this what is the underlying cause of the problem. > > There may be something wrong in how we use setjmp/longjmp or how > > setjmp/longjmp works on Windows. > > > > It reminds me of a problem I've been debugging few days ago, when > > longjump implementation segfaults on Windows 10 (recent but not > > Insider build) probably soon after unwinding the stack, but only with > > GCC 10 / MinGW 7 and only in one of the no-segfault tests, and only > > with -03 (not -O2, not with with -O3 -fno-split-loops). The problem > &gt...

...we use setjmp/longjmp for our exception handling on all platforms in our regular (non-LLVM) code generators. I'd like to use the same infrastructure with the LLVM code generator for code interoperability purposes (the LLVM SjLj personality is not binary-compatible with our existing setjump/longjump buffers). What I did was: 1) create a dummy personality function in our run time library that basically always says "no, this frame does not wish to handle this exception nor does it have any clean-up code", and specify it as personality function for any function that deals with excep...

...r, due to the issues with continuing > >>> to keep the main archive on kernel.org, I have moved the release archive to: > >> > >> Please add a non ancient gnu-efi snapshot too. > >> > >> Jocke > > > > You vill need two commits( Update the longjump calls to fit the new declaration, The VPrint definition is now part of the exports of gnu-efi) > > from https://github.com/joakim-tjernlund/syslinux/commits/master > > to build against a modern gnu-efi > > > > Hi, > > I merged your tree and added the install patch on t...

...s what is the underlying cause of the problem. >>>> There may be something wrong in how we use setjmp/longjmp or how >>>> setjmp/longjmp works on Windows. >>>> >>>> It reminds me of a problem I've been debugging few days ago, when >>>> longjump implementation segfaults on Windows 10 (recent but not >>>> Insider build) probably soon after unwinding the stack, but only with >>>> GCC 10 / MinGW 7 and only in one of the no-segfault tests, and only >>>> with -03 (not -O2, not with with -O3 -fno-split-loops)....

...t is not an IR example, but rather a LLVM IR API example. It would be interesting to see a pure IR version of a personality function. I don't see why this would not be possible, although costly in terms of effort. Clang would help. There are also ways to lower your invoke/unwind into a setjump/longjump implementation, but I do not know how to do this in IR, as it requires function pass setup which is outside the scope of IR. Garrison On Jan 13, 2010, at 4:40, Dustin Laurence wrote: > I put invoke/unwind aside because I couldn't get them to work, but I'm > working on my evaluator...

I put invoke/unwind aside because I couldn't get them to work, but I'm working on my evaluator now and it would be nice to figure this out so I don't have to unwind the stack manually. This was the reason for my earlier question about global declarations, and as that's cleared up I can easily pass exception data...if I can make unwind return out of some deep recursion. The

...LVM syntax is simple enough that it could be done without parsing the IR. I don't know if I have enough IR left to justify switching over, but it would be satisfying in principle to get rid of the duplication of headers. > There are also ways to lower your invoke/unwind into a > setjump/longjump implementation, but I do not know how to do this in > IR, as it requires function pass setup which is outside the scope of > IR. I don't know enough about how setjmp/longjmp are implemented to have a clue. If I'm getting into uncharted territory it's easier to just unwind the ev...

...syslinux-6.04-pre2 release, however, due to the issues with continuing >>> to keep the main archive on kernel.org, I have moved the release archive to: >> >> Please add a non ancient gnu-efi snapshot too. >> >> Jocke > > You vill need two commits( Update the longjump calls to fit the new declaration, The VPrint definition is now part of the exports of gnu-efi) > from https://github.com/joakim-tjernlund/syslinux/commits/master > to build against a modern gnu-efi > Hi, I merged your tree and added the install patch on top of it. Thank you! -hpa

...t; > > > to keep the main archive on kernel.org, I have moved the release archive to: > > > > > > > > Please add a non ancient gnu-efi snapshot too. > > > > > > > > Jocke > > > > > > You vill need two commits( Update the longjump calls to fit the new declaration, The VPrint definition is now part of the exports of gnu-efi) > > > from https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjoakim-tjernlund%2Fsyslinux%2Fcommits%2Fmaster&amp;data=02%7C01%7CJoakim.Tjernlund%40infinera.com%7C1a...

...ned by the program is 0xC0000028, which is STATUS_BAD_STACK with the description: "An invalid or unaligned stack was encountered during an unwind operation". I'm not really good at C++ or makefile/compiler stuff, but I can't get it to work. I'm guessing this as to do with some longjumps to return to the prompt when there is an error but I don't know how to fix it. Compiling in 32 bits: P:/Rtools/mingw_32/bin/g++ -O3 -Wall -pedantic -IP:/R/R-3.4.3/include -c testr.cpp -o testr.o P:/Rtools/mingw_32/bin/g++ -o ./32.exe ./testr.o -LP:/R/R-3.4.3/bin/i386 -lR -lRgraphapp Results...

...pointer and engine instance, retrieves the jitted C pointer, and calls it. - As this pointer is a pointer to fc, the unwind is then executed. Basically I have the call stack fa->fb->fc with fa, fc generated and fb not generated. Given that I was using the intuitive model of a setjump, longjump, I thought that fc's unwind would pass through fb and end up at fa's invoke's exception block. However it cores even though I've verified that each function is being executed. So I guess either there is something fundamental I don't understand, or I have another issue....

...nk we will need to eventually spend some time re-examining how we want to handle interrupts. Right now on Windows/Mac interrupts are only processed at special points in the evaluation process, which is a bit restrictive (but perhaps unavoidable due to OS limitations). On UNIX on the other hand we LONGJUMP out of the signal handler except for the very few places where the signal gets masked temporarily (GC and one place in graphics I believe). The UNIX approach is much too loose even now, and it becomes even more untenable if we add any kind of threading support. We will I think have to come up wit...

...her, it just does a longjmp, same as R, which can result in leaking memory, and possibly other bad things. The way Bash handles this is to only set a flag in the handler for SIGINT, then at safe places in the code, there are QUIT; statements. These are macros that expand to some code that may longjump somewhere depending on the interrupt state. This method avoids the problems of jumping out of the signal handler, which may result in memory leaks or inconsistencies in global state. The hard part is inserting the (many!) QUIT statements, though it is probably somewhat easier if this type of choi...