similar to: Continuing from dbgtrap on different targets

Displaying 20 results from an estimated 1100 matches similar to: "Continuing from dbgtrap on different targets"

2008 Jan 13
2
{worker} after :end-time worker freaks out
Hi all, i was using bdrb a while ago and it wasn''t stable enough in version 0.2.1 for doing the job - it loss jobs or did execute only the first one invoked and so on. Now i gave the new version a try and i found a bug at playing around. When i start a worker_method over the normal Unix scheduler bdrb will start as much as possible the worker_method after the :end-time is reached.
2020 Mar 05
2
[lldb-dev] Continuing from dbgtrap on different targets
On 04/03/2020 21:45, Jim Ingham via llvm-dev wrote: > As you have seen, different machine architectures do different things after hitting a trap. On x86_64, the trap instruction is executed, and then you stop, so the PC is left after the stop. On arm64, when execution halts the pc is still pointing at the trap instruction. > > I don't think lldb should be in the business of telling
2013 Nov 21
3
[LLVMdev] ErrorOr<> conflicts with unique_ptr<>
Michael, In lld, we have places that used nested a ErrorOr<std::unique_ptr<xx>> and I often hit compiler errors that require breaking up expressions to work around. Do you have suggestions on how to code the following simple examples to not error? Can some of these be fixed in ErrorOr.h? Or am I totally not getting something? -Nick struct Foo { void doit(); };
2013 Nov 22
0
[LLVMdev] ErrorOr<> conflicts with unique_ptr<>
On Thu, Nov 21, 2013 at 3:57 PM, Nick Kledzik <kledzik at apple.com> wrote: > Michael, > > In lld, we have places that used nested a ErrorOr<std::unique_ptr<xx>> and > I often hit compiler errors that require breaking up expressions to work > around. Do you have suggestions on how to code the following simple > examples to not error? Can some of these be
2013 May 26
1
[LLVMdev] How to always generate epilogue code?
Hi! I am still working on the Win64 EH code and now have a pretty usable result. (The MC part is already posted to llvm-commits, the other part follows soon. If you are curious the whole patch is here: http://www.redstar.de/ldc/win64eh_all_20130524.diff.) However, in one case I have a problem with LLVM being too smart. Consider the following D code: void doIt() { printf("doIt:
2002 Apr 29
1
Garbage collection: RW1041
Have searched through the archives but have been unable to find any related issues - hopefully I'm not bringing up an old topic. Am using RW1041 on a Windows NT on a machine with 1Gb of memory. Have a function doit() that reads in a chunk of data using readBin, performs a regression, saves out coeffs and then returns. When using Rgui with the default memory limit of 256Mb I'm able to
2013 Nov 22
3
[LLVMdev] ErrorOr<> conflicts with unique_ptr<>
On Nov 21, 2013, at 4:07 PM, David Blaikie <dblaikie at gmail.com> wrote: > > > > On Thu, Nov 21, 2013 at 3:57 PM, Nick Kledzik <kledzik at apple.com> wrote: > Michael, > > In lld, we have places that used nested a ErrorOr<std::unique_ptr<xx>> and I often hit compiler errors that require breaking up expressions to work around. Do you have
1999 Dec 13
3
t.test inside function (PR#373)
Full_Name: Bill Simpson Version: 65.1 OS: linux Submission from: (NULL) (193.62.250.209) Try this code as separate lines entered interactively, then try doit() doit<-function() { x<-seq(1,10) y1<-x+rnorm(10,1,1.5) y2<-x+rnorm(10,1,1) t.test(x,y1,paired=TRUE) t.test(x,y2,paired=TRUE) } doit() apparently executes only the last of a series of t.test()s. Maybe this is no bug,
2010 Jul 19
3
invalid type error
>myDF = data.frame(id=c("A10","A20"),d1=c(.3,.3),d2=c(.4,.4),d3=c(-.2,.5),d4=c(-.3,.6),d5=c(.5,-.2),d6=c(.6,-.4),d7=c(-.9,-.5),d8=c(-.8,-.6)) >doit=function(x)c(x[1],sum_LK_positive=sum(x[-1][x[-1]>0]),sum_LK_negative=sum(x[-1][x[-1]<0])) > myDF id d1 d2 d3 d4 d5 d6 d7 d8 1 A10 0.3 0.4 -0.2 -0.3 0.5 0.6 -0.9 -0.8 2 A20 0.3 0.4 0.5 0.6 -0.2
2008 Aug 04
1
R init file and source()
In the context of calling R from another program (namely gretl, http://gretl.sourceforge.net ) I'm trying to understand the interactions of the R init file (corresponding to the environment variable RPROFILE) and the source() function. I'll illustrate my problem with the following simplified contrast implemented in the bash shell (with R 2.7.1). 1. Works fine: allin at myrtle:~/Rfoo$
2023 Mar 16
3
Trying to learn how to write an "advanced" function
Although I owe thanks to Ramus and Ivan, I still do not know how to write and "advanced" function. My most recent try (after looking at the material Ramus and Ivan set) still does not work. I am trying to run the lm function on two different formulae: 1) y~x, 2) y~x+z Any corrections would be appreciated! Thank you, John doit <- function(x){ ds <- deparse(substitute(x))
2009 Jun 23
3
V2.9.0 changes [Sec=Unclassified]
Hi all, Prefix: I am a frustrated Java coder in R. I am coding a medium sized ecosystem modelling program in R. I have changed to using S4 objects and it has cost me an order of magnitude in execution speed over the functional model. I cannot afford this penalty and have found that it is the result of all the passing-by-value of objects. I see that you can now safely inherit from
2010 Jul 27
4
re-sampling of large sacle data
myDF: d1 d2 d3 d4 d5 -0.166910351 0.022304377 -0.00825924 0.008330689 -0.000925938 -0.166910351 0.022304377 -0.00825924 0.008330689 -0.000925938 -0.166910351 0.022304377 -0.00825924 0.008330689 -0.168225938 -0.166910351 0.022304377 -0.00825924 0.008330689 -0.168225938 -0.166910351 0.022304377 -0.00825924 0.008330689 -0.168225938 -0.166910351
2004 Apr 02
2
[LLVMdev] Function pointers
OK, I solved it all ( so far :) ), mixing in some load-instructions and called on the result of that, which worked. Here is the skeleton-code: %kernel = type { int ()* } int puts_kernel(){...} ; main() %theKernel = malloc %kernel %puts_kernelPTR = getelementptr %kernel* %theKernel, long 1, ubyte 0 store int ()* %puts_kernel, int ()** %puts_kernelPTR %tmp.11 = load int ()** %puts_kernelPTR
2004 Apr 02
0
[LLVMdev] Function pointers
On Fri, 2 Apr 2004, Anders Alexandersson wrote: > OK, I solved it all ( so far :) ), mixing in some load-instructions and > called on the result of that, which worked. > > Here is the skeleton-code: > > %kernel = type { int ()* } > > int puts_kernel(){...} > > ; main() > > %theKernel = malloc %kernel > %puts_kernelPTR = getelementptr %kernel* %theKernel,
2007 Nov 07
1
Aggregate with non-scalar function
R-Helpers, I'm sorry to have to ask this -- I've not used R very much in the last 8 or 10 months, and I've gotten rusty. I have the following (ff2 is a subset of a much, much larger dataset): > ff2 hostName user sys idle obsTime 10142 fred 0.4 0.5 98.0 2007-11-01 02:02:18 16886 barney 0.5 0.2 94.6 2007-10-25 19:12:12 8795 fred 0.0 0.1 99.8
2018 Feb 24
1
Parsing a bit code file
I am trying to parse LLVM IR from a bit code file. I went through the following steps. hello.cpp #include <iostream> int main() { std::cout << "Hello world!" << "\n"; return 0;} dump.cpp #include <llvm/IR/Module.h>#include <llvm/IRReader/IRReader.h>#include <llvm/IR/LLVMContext.h>#include <llvm/Support/SourceMgr.h> using
2011 Aug 24
2
[LLVMdev] VMKit Development
Hi, Going ahead, the llvm-ld seems to segfault (build on Linux with llvm-ld v3.0svn build): make[2]: Entering directory `/root/code/vmkit/mmtk/mmtk-j3' llvm[2]: Building Debug+Asserts Bytecode Module MMTKRuntime.bc 0 llvm-ld 0x0884c66e 1 llvm-ld 0x0884c3fb 2 0xb7891400 __kernel_sigreturn + 0 3 llvm-ld 0x083be9e9 llvm::isa_impl<llvm::Constant,
2004 Jun 23
0
[LLVMdev] weird issue with mem2reg
MetaSplit is an anlysis I just finished writing. It doesn't alter anything, all it does is build a set of "program instructions". For some reason even though if I run it with any other combination of passes I've found, anytime I run it with mem2reg I get a seg fault in dyn_cast! Here's output: Starting program: /mounts/zion/disks/0/localhome/pmeredit/llvm/tools/Debug/opt
2004 Jun 23
2
[LLVMdev] weird issue with mem2reg
On Wed, 23 Jun 2004, Patrick Meredith wrote: > MetaSplit is an anlysis I just finished writing. It doesn't alter anything, > all it does is build a set of "program instructions". For some reason even > though if I run it with any other combination of passes I've found, anytime > I run it with mem2reg I get a seg fault in dyn_cast! Here's output: > >