search for: ccall

...ttice: If lattice is _not_ attached, I get > lattice::dotplot(~1:10) Error in eval(expr, envir, enclos) : could not find function "bwplot" This happens because of this: > lattice:::dotplot.formula function (x, data = NULL, panel = "panel.dotplot", ...) { ocall <- ccall <- match.call() ccall$data <- data ccall$panel <- panel ccall[[1]] <- as.name("bwplot") ans <- eval.parent(ccall) ans$call <- ocall ans } <environment: namespace:lattice> That is, ccall is eval()-ed in the global environment where bwplot is...

The code for ccall looks right. Sounds like you have a very small range of instructions where an uninitialized value appear. You could try debugging at asm level. Shadow for b should be passed at offset 0 in __msan_param_tls. MSan could propagate shadow through arithmetic and even some logic operations (like select)...

I have the following procedure which worked just fine for in R 2.2.0. Recently I upgraded to 2.6.1 and now get an error: > ScatterOutlier(pass_500_506[1:1000,6:12], marginal_500_506[,6:12]) Error in eval(expr, envir, enclos) : object "out" not found Note that I use the same workspace (and hence data) as in 2.2.0. When I make sure that the object "out" exists at

...", module.get()); // Body of the `a` function { /// @brief Set entry label llvm::BasicBlock *block = llvm::BasicBlock::Create(context, "entry", aFun); /// @brief builder llvm::IRBuilder<> builder(block); builder.SetInsertPoint(block); llvm::CallInst *cCall = builder.CreateCall(cFun, {}, "c"); llvm::Value *res = cCall; builder.CreateRet(res); llvm::verifyFunction(*aFun); } // Body of the `b` function { /// @brief Set entry label llvm::BasicBlock *block = llvm::BasicBlock::Create(context, "entry", bFun);...

...p;ptr,8) > ff ff ff ff ff ff ff ff > o: 40000e23 o: 80007614 > $22 = void > > Notice the origin of the lower bits is off. Any idea as to why? > > > On Mon, Feb 3, 2014 at 2:52 AM, Evgeniy Stepanov < > eugeni.stepanov at gmail.com> wrote: > >> The code for ccall looks right. Sounds like you have a very small >> range of instructions where an uninitialized value appear. You could >> try debugging at asm level. Shadow for b should be passed at offset 0 >> in __msan_param_tls. >> >> MSan could propagate shadow through arithmetic...

...22 = void > >> > >> Notice the origin of the lower bits is off. Any idea as to why? > >> > >> > >> On Mon, Feb 3, 2014 at 2:52 AM, Evgeniy Stepanov > >> <eugeni.stepanov at gmail.com> wrote: > >>> > >>> The code for ccall looks right. Sounds like you have a very small > >>> range of instructions where an uninitialized value appear. You could > >>> try debugging at asm level. Shadow for b should be passed at offset 0 > >>> in __msan_param_tls. > >>> > >>> MS...

...clockwise = clockwise, init.angle = init.angle, angle = angle, density = density, col = col, border = border, lty = lty) } piechart <- function(x, data = NULL, panel = "panel.piechart", ...) { ocall <- sys.call(sys.parent()) ocall[[1]] <- quote(piechart) ccall <- match.call() ccall$data <- data ccall$panel <- panel ccall$default.scales <- list(draw = FALSE) ccall[[1]] <- quote(lattice::barchart) ans <- eval.parent(ccall) ans$call <- ocall ans } ## Figure 14.5 par(new = TRUE) piechart(foo) Thanks in advan...

How is ccall() implemented? If it manually sets up a stack frame, then it also needs to store argument shadow values in paramtls. I don't think there is an overflow, unless you have a _lot_ of arguments in a function call. On Sun, Feb 2, 2014 at 9:26 AM, Keno Fischer <kfischer at college.harvard.edu&gt...

As you may not be surprised to hear, no sooner did I post the previous message than I realized I had a really dumb mistake. I've now gotten a bit farther but am still stuck. New code: graph <- function (x, data, groups, xlab) { pg <- function(x, y, group.number, ...) fnord body(pg) <- substitute({ panel.xyplot(x, y, ..., group.number=group.number) panel.text(2,

...9;t remember off the top of my head why I had to use a custom context as opposed to sending it to the SIP provider directly, but I'm pretty sure there was a reason. Here's the custom context: [hosted-1004-outcall] exten => _NXXNXXXXXX,1,Dial(SIP/sip-provider/+1${EXTEN},60,rU(hosted-1004-ccall)) same => n,Busy() Now, whenever I want to forward a call to a cell phone (or more), I use: Dial(Local/5555551212 at hosted-1004-outcall &Local/5555551213 at hosted-1004-outcall) This sends the call to both phones simultaneously, using the above Dial() code. As you can see, I'm using...

...t;Dec.03","Jan.04","Feb.04","Mar.04", "Apr.04","May.04","Jun.04","Jul.04","Aug.04","Sep.04", "Oct.04")),direction = "long") The second dataset contains the variables es(Ccalls) [1] "TERRITORY" "REGION" "ACTIVITY_TYPE" [4] "CONTACT_TYPE" "TARGETED_FLG" "CONTACT_GRADE" [7] "CONTACT_PR_SPECIALITY" "UBM" "DEC0...

An embedded and charset-unspecified text was scrubbed... Name: inte tillg?nglig URL: <https://stat.ethz.ch/pipermail/r-help/attachments/20110811/f20d8760/attachment.pl>

...ptimized out>, nargs=1, >> >> nargs at entry=<optimized out>) at ./julia.h:1043 >> >> >> >> (here's the code of that julia function for reference) >> >> >> >> isempty(s::IntSet) = >> >> !s.fill1s && ccall(:bitvector_any1, Uint32, (Ptr{Uint32}, Uint64, >> >> Uint64), s.bits, 0, s.limit)==0 >> >> >> >> Looking at where that value is coming from: >> >> >> >> (gdb) f 5 >> >> #5 0x00007f417c163e3d in jl_apply (f=0x606000984d60, f at...

...in jl_apply (f=0x606000984d60, f at entry=<optimized out>, args=0x7fff9132da20, args at entry=<optimized out>, nargs=1, nargs at entry=<optimized out>) at ./julia.h:1043 (here's the code of that julia function for reference) isempty(s::IntSet) = !s.fill1s && ccall(:bitvector_any1, Uint32, (Ptr{Uint32}, Uint64, Uint64), s.bits, 0, s.limit)==0 Looking at where that value is coming from: (gdb) f 5 #5 0x00007f417c163e3d in jl_apply (f=0x606000984d60, f at entry=<optimized out>, args=0x7fff9132da20, args at entry=<optimized out>, nargs=1, nargs...

...> out>, args=0x7fff9132da20, args at entry=<optimized out>, nargs=1, >> nargs at entry=<optimized out>) at ./julia.h:1043 >> >> (here's the code of that julia function for reference) >> >> isempty(s::IntSet) = >> !s.fill1s && ccall(:bitvector_any1, Uint32, (Ptr{Uint32}, Uint64, >> Uint64), s.bits, 0, s.limit)==0 >> >> Looking at where that value is coming from: >> >> (gdb) f 5 >> #5 0x00007f417c163e3d in jl_apply (f=0x606000984d60, f at entry=<optimized >> out>, args=0x7fff9132...

hi all after getting some (or - a lot) of messages from nagios, claiming asterisk to be down, I found this out... astping xxx times repeatedly, and the manager fails to start. this little script was used for testing. below, I've pasted the output from 'ps axfv' before and after the DoS, showing asterisk having allocated ~2GB RAM. roy #!/usr/bin/perl -w use strict; my $i = 0;

...(* Generate wrappers for each foreign function. *) List.iter ( - fun { name = name; style = (ret, args, optargs as style); + fun { name; style = (ret, args, optargs as style); c_function = c_function } -> if can_generate style then ( pr "foreign import ccall unsafe \"guestfs.h %s\" c_%s\n" diff --git a/generator/java.ml b/generator/java.ml index 94d68c14a..308f65bd8 100644 --- a/generator/java.ml +++ b/generator/java.ml @@ -614,7 +614,7 @@ throw_out_of_memory (JNIEnv *env, const char *msg) "; List.iter ( - fun { name = name...

Per my previous email: https://www.redhat.com/archives/libguestfs/2017-September/msg00203.html I'd like to talk about requiring a more modern version of the OCaml compiler. These commits show some of the code changes which would be possible with OCaml >= 3.12 [which it turns out we already require by accident] and also with OCaml >= 4.02. The latter is my favoured option. Rich.

...[i].%s);\n" name; ) cols; pr " (*env)->SetObjectArrayElement (env, jfl, i, jfl);\n"; pr " }\n"; @@ -8579,71 +8579,71 @@ last_error h = do List.iter ( fun (name, style, _, _, _, _, _) -> if can_generate style then ( - pr "foreign import ccall unsafe \"guestfs_%s\" c_%s\n" name name; - pr " :: "; - generate_haskell_prototype ~handle:"GuestfsP" style; - pr "\n"; - pr "\n"; - pr "%s :: " name; - generate_haskell_prototype ~handle:"GuestfsH" ~hs:true style; - pr &qu...