similar to: longjmp - was: seemingly random "nesting of readline input" w arnings

Mosix is a cluster operating system that is a set of kernel patches to Linux on i386 machines. It allows processes to migrate to other nodes on the cluster transparently. See www.mosix.org for details. However, my R processes were refusing to migrate. Using strace, and delving into the R code, I found that it was due to a large number of calls to the system setjmp and longjmp routines - the

I'm trying to get unwind to work. I was unable to get an unwind example to work directly, so I decided to compile a c program that uses setjmp and longjmp and work backwards. I keep running into a "Abort trap" problem, whatever "Abort trap" is. Anyway, here's an example of a C program that compiles and works properly under normal gcc, but that fails with an

It seems straightforward to implement, if it just needs to be functionally correct. I have another question about setjmp/longjmp. When the following program is compiled and run with argument 10 (./a.out 10), should it print 10 or 23? I am asking this question because it prints 23 when compiled with gcc and prints 10 when compiled with clang. If it is supposed to return 23, it seems to me that

On Wed, 20 Apr 2005, Greg Pettyjohn wrote: > I'm trying to get unwind to work. > > I was unable to get an unwind example to work directly, > so I decided to compile a c program that uses setjmp > and longjmp and work backwards. > > I keep running into a "Abort trap" problem, whatever "Abort trap" is. > > Anyway, here's an example of a C

First I try it with bytecodes: ~/compiler/temp$ llvmgcc sjmp01.c -o sjmp01 ~/compiler/temp$ ./sjmp01 Hello World! Abort trap Same results for lli sjmp01.bc Now I try converting to native code: ~/compiler/temp$ llc sjmp01.bc -enable-correct-eh-support -o sjmp01.s ~/compiler/temp$ gcc sjmp01.s -o sjmp01.native ~/compiler/temp$ ./sjmp01.native Hello World! Bus error ~/compiler/temp$ On Apr 20,

On Apr 12, 2011, at 3:15 PM, Jim Grosbach wrote: > If you want an automated method, then using the source code re-writer interfaces in clang is probably a reasonable starting place. Just modifying the source code manually is probably easier, though, to be honest. > > As a moderate caveat to all of this, there are some bits of code out there that use these builtins that are very tightly

On Mon, 2018-12-17 at 23:52 +0100, Lukas Schwaighofer wrote: > CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. > > > Hi Joakim, > > On Wed, 12 Dec 2018 23:25:24 +0000 > Joakim Tjernlund via Syslinux <syslinux at zytor.com> wrote: > > > I

On Mon, 21 Nov 2005 16:53:58 -0600 (CST), Chris wrote: >On Mon, 21 Nov 2005, Kurt Harriman wrote: >> I would like to build an x86 executable consisting of a number of >> subsystems (mostly legacy C code). One subsystem will be compiled >> to native code using llvm. It calls, and is called by, the other >> subsystems, many of which have to be compiled using gcc

From: Martin Maechler <maechler at stat.math.ethz.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17739.46076.735981.117358 at stat.math.ethz.ch> Date: Fri, 3 Nov 2006 22:26:20 +0100 To: Barry Rowlingson <B.Rowlingson at lancaster.ac.uk> Cc: Sarah Goslee <sarah.goslee at gmail.com>, r-help at

Full_Name: Barry Rowlingson Version: 1.6.0 OS: RH8 i386 Submission from: (NULL) (148.88.136.205) Strange things happen if I premultiply a difftime() object with a number. Example: > d1 <- difftime(Sys.time(),Sys.time()) > d2 <- 1 * difftime(Sys.time(),Sys.time()) > d3 <- difftime(Sys.time(),Sys.time()) * 1 > d1 Time difference of 0 secs - thats fine > d2 [1] 0

Commit-ID: edf92a18d1f1725896c928cbcf580abc268f307c Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=edf92a18d1f1725896c928cbcf580abc268f307c Author: James Cowgill <james.cowgill at mips.com> AuthorDate: Fri, 2 Mar 2018 08:33:03 -0800 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Wed, 2 Jan 2019 03:08:04 +0000 [klibc] mips: don't save

I see some value in Duncan?s proposal to implement this as an extra package instead of a change to base R, if only to see if the idea has legs. I?m minded to do so myself using your suggestion, but is there a particular reason why you recommend using the remotes package instead of devtools? The latter seems to have the same functions I would need, and I believe it is more widely installed that

Recently, while using R-patched and now R-1.6.1 (on RedHat Linux 7.1) I've been getting the following warning in the course of everyday activity: [... some R activity ...] In addition: Warning message: An unusual circumstance has arisen in the nesting of readline input. Please report using bug.report() > The warning is difficult to reproduce because it seems to appear at random times,

On Mon, Mar 8, 2010 at 8:46 PM, Barry Rowlingson <b.rowlingson at lancaster.ac.uk> wrote: > On Mon, Mar 8, 2010 at 6:44 PM, Ma Ismail - NewYork-MEAG-NY > <ima at meag-ny.com> wrote: >> Hi, >> >> A few of the developers on our Quant team are using R for data calculation and to generate a [snip] > ?I've noticed a lot of financial corporates getting into R

Thanks to the hard work of Bill Wendling (wendling at isanbard.org), LLVM now translates setjmp/longjmp calls into the LLVM "exception handling" instructions invoke & unwind. This means that all of the LLVM optimizers are now aware of the extra control flow edges made possible by setjmp & longjmp, so data flow analyses won't make incorrect transformations. A variety of

From: Sylvain Gault <sylvain.gault at gmail.com> Hello there, I propose 2 patches that fix two possible stack overflows either when running a COM32 module or when loading a new config file. I didn't find a better way to do this than to use the infamous setjmp/longjmp functions to restore the stack to a previous state. This makes the logic a bit more complex, but the behavior is not

Hi, I would like to build an x86 executable consisting of a number of subsystems (mostly legacy C code). One subsystem will be compiled to native code using llvm. It calls, and is called by, the other subsystems, many of which have to be compiled using gcc because they use small amounts of inline assembly. All of the subsystems catch and throw errors to one another using setjmp/longjmp. When

On Thu, 26 Jul 2018, G?bor Cs?rdi wrote: > On Thu, Jul 26, 2018 at 12:25 PM Barry Rowlingson > <b.rowlingson at lancaster.ac.uk> wrote: >> >> On Thu, Jul 26, 2018 at 12:22 AM, G?bor Cs?rdi <csardi.gabor at gmail.com> wrote: >>> I am trying to control a background R session, connected via a fifo / >>> named pipe. >> >> Is the fifo

[klibc] [PATCH] fix ARM longjmp with zero 'val'. We need to set the condition codes on the ARM. The previous version was using a left over condition code from the caller. Also, use conditional execution to eliminate branch and reduce size. Signed-off-by: Bill Pringlemeir <bpringle at sympatico.ca> diff --git a/usr/klibc/arch/arm/setjmp.S b/usr/klibc/arch/arm/setjmp.S index

Commit-ID: d7d16afbdae9bdea83aeb26ac572e6fc4d7d4940 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=d7d16afbdae9bdea83aeb26ac572e6fc4d7d4940 Author: Steve McIntyre <steve at einval.com> AuthorDate: Fri, 29 Jun 2012 18:13:34 +0100 Committer: maximilian attems <max at stro.at> CommitDate: Sun, 1 Jul 2012 22:51:00 +0200 [klibc] arm/setjmp.S: fix longjmp