search for: l94

...at memory allocated by Calloc/Realloc comes from the same pool as used by malloc: in particular do not use free or strdup with it." I think the reason is that R uses dlmalloc for Calloc on Windows: https://github.com/wch/r-source/blob/c634fec5214e73747b44d7c0e6f047fefe44667d/src/main/memory.c#L94-L103

...s coef(lme4:::summary.merMod(fm1B)) ## table without df and p values is(fm1B,"merMod") ## TRUE library(broom) tidy(fm1B) ## hard to show what's going on without debugging through the function: ## the issue occurs here: ## https://github.com/dgrtwo/broom/blob/master/R/lme4_tidiers.R#L94 I can't replicate this behaviour with a trivial method ... silly <- function(x, ...) { UseMethod("silly") } silly.merMod <- function(object, ...) { coef(summary(object)) } silly(fm1B) environment(silly) <- environment(tidy) silly(fm1B)

..._mdev_features)(struct mdev_device *mdev); Do we need a .set_mdev_features method as well? It's not very clear what does mdev_features mean. Does it mean the vhost backend features? https://github.com/torvalds/linux/blob/0e2adab6cf285c41e825b6c74a3aa61324d1132c/include/uapi/linux/vhost.h#L93-L94 > + u32 (*get_generation)(struct mdev_device *mdev); > +}; > + > +void mdev_set_virtio_ops(struct mdev_device *mdev, > + const struct virtio_mdev_device_ops *virtio_ops); > + > +#endif > -- > 2.19.1 >

...oc comes from the same pool as used by >> malloc: in particular do not use free or strdup with it." >> >> I think the reason is that R uses dlmalloc for Calloc on Windows: >> https://github.com/wch/r-source/blob/c634fec5214e73747b44d7c0e6f047fefe44667d/src/main/memory.c#L94-L103 > > But that section #defines calloc and free to Rm_... counterparts in lockstep? (I assume that is where dlmalloc comes in?) > > Anyways, does it actually work to change free() to Free()? If so, then all this post mortem analysis is rather a moot point. > > -pd > > --...

...by Calloc/Realloc comes from the same pool as used by > malloc: in particular do not use free or strdup with it." > > I think the reason is that R uses dlmalloc for Calloc on Windows: > https://github.com/wch/r-source/blob/c634fec5214e73747b44d7c0e6f047fefe44667d/src/main/memory.c#L94-L103 But that section #defines calloc and free to Rm_... counterparts in lockstep? (I assume that is where dlmalloc comes in?) Anyways, does it actually work to change free() to Free()? If so, then all this post mortem analysis is rather a moot point. -pd -- Peter Dalgaard, Professor, Center f...

...t; M"D=R87!H:6-S1')I=F5R/7@Q,61R=@IP<FEN=&5R/6]F9@H*6W@Q,61R=ET* M06QL;V-3>7-T96U#;VQO<G,@/2`Q,#`*4')I=F%T94-O;&]R36%P(#T@3@I0 M97)F96-T9W)A<&AI8W,@/2!."DUA;F%G960@/2!."E5S941'02`](%D*57-E M6'-H;2`](%D@"D181W)A8B`]($X*1&5S:W1O<$1O=6)L94)U9F9E<F5D(#T@ +60I497AT0U`],`H` ` end

...ob/master/daemon/command.c#L148-L215 (eg. the "renaming ... to ..." messages should appear). Question is why does /etc/resolv.conf not get created? On Fedora, it is created by dhclient running from appliance/init: https://github.com/libguestfs/libguestfs/blob/master/appliance/init#L88-L94 On Debian/Ubuntu that is supposed to run dhclient if available or dhcpcd if not. Run `./run virt-rescue --network --scratch' on the Ubuntu host and see if: - either dhclient or dhcpcd exists in the appliance - they work when you run them, or if there is an error message - if running one...

...same pool as used by >>> malloc: in particular do not use free or strdup with it." >>> >>> I think the reason is that R uses dlmalloc for Calloc on Windows: >>> https://github.com/wch/r-source/blob/c634fec5214e73747b44d7c0e6f047fefe44667d/src/main/memory.c#L94-L103 >> >> But that section #defines calloc and free to Rm_... counterparts in lockstep? (I assume that is where dlmalloc comes in?) >> >> Anyways, does it actually work to change free() to Free()? If so, then all this post mortem analysis is rather a moot point. >>...

...pace_1.2-6 stringi_1.1.1 acepack_1.3-3.3 [41] munsell_0.4.3 chron_2.3-47 > > ## hard to show what's going on without debugging through the function: > ## the issue occurs here: > ## https://github.com/dgrtwo/broom/blob/master/R/lme4_tidiers.R#L94 > I can't replicate this behaviour with a trivial method ... > silly <- function(x, ...) { > UseMethod("silly") > } > silly.merMod <- function(object, ...) { > coef(summary(object)) > } > silly(fm1B) > environment(...

On 03/13/2015 11:13 AM, Richard W.M. Jones wrote: > > Yes, the log indicates name resolution not working. Please try the > diagnosis steps that I outlined in: > > https://www.redhat.com/archives/libguestfs/2015-March/msg00075.html Sorry, I somehow missed the above message. $ ./run guestfish get-backend direct Here are the outputs of the /dev/tcp test, first doing: $ ./run

...ibdovecot.so: linked to /home/henrikj/Build/dovecot-2.1.15/src/lib-dovecot/.libs/libdovecot.so: attempted multiple inclusion of file Undefined first referenced symbol in file $XBKaiwbjOCHRV5w.array_append_array_i..L93 dsync/libdsync.a(dsync-brain.o) $XBKaiwbjOCHRV5w.array_append_array_i..L94 dsync/libdsync.a(dsync-brain.o) $XBKaiwbjOCHRV5w.array_append_array_i..L95 dsync/libdsync.a(dsync-brain.o) ld: fatal: symbol referencing errors. No output written to .libs/doveadm *** Error code 2 make: Fatal error: Command failed for target `doveadm' Current working directory /home/henrikj/Bui...

On 21 Apr 2018, at 22:19, Chris Lattner via llvm-dev <llvm-dev at lists.llvm.org> wrote: > >> >> On Apr 20, 2018, at 2:06 AM, Csaba Raduly via cfe-dev <cfe-dev at lists.llvm.org> wrote: >> >> On 4/20/18, James Y Knight wrote: >>> >>> >>> Yep. "-fnull-pointer-is-valid" has been suggested before. >>> >>

> On Apr 20, 2018, at 2:06 AM, Csaba Raduly via cfe-dev <cfe-dev at lists.llvm.org> wrote: > > On 4/20/18, James Y Knight wrote: >> >> >> Yep. "-fnull-pointer-is-valid" has been suggested before. >> > > -fplacate-linux-kernel-developers ? Please, lets keep this discussion on topic and productive. The semantics described upstream of (the

On Thu, Jan 17, Richard W.M. Jones wrote: > On Wed, Jan 16, 2013 at 05:51:53PM +0100, Olaf Hering wrote: > > On Mon, Jan 14, Olaf Hering wrote: > > > This is a first attempt to build libguestfs with just a ocaml bytecode > > > compiler. The three tools written in ocaml will be build only when an > > > ocamlopt compiler is available. > > Here is a more

So this wasn't tested for a month? Anyways, Free() is just free() with a check that we're not freeing a null pointer, followed by setting the pointer to NULL. At that point of tcltk.c, we have for (objc = i = 0; i < length(avec); i++){ const char *s; char *tmp; if (!isNull(nm) && strlen(s = translateChar(STRING_ELT(nm, i)))){ // tmp =

> On Feb 29, 2016, at 10:50 PM, Hal Finkel <hfinkel at anl.gov> wrote: > > > > From: "Mehdi Amini via llvm-dev" <llvm-dev at lists.llvm.org> > To: "Alina Sbirlea" <alina.sbirlea at gmail.com> > Cc: "llvm-dev" <llvm-dev at lists.llvm.org> > Sent: Monday, February 29, 2016 7:06:51 PM > Subject: Re: [llvm-dev] RFC:

Hi, I''ve got a newbie question--sorry if this is covered elsewhere, I parsed through the archives for awhile and didn''t see it. I''d like to listen for whenever a file is renamed (e.g. foo.txt -> foo.old) and then magically change it back. This sounds odd, but I''m working with a stubborn application and this will actually make things work nice. So, if I do:

...amp;%T:6]N($YO+TYO.B`B)5-#25!01#H@1$9%(%1"7T-O;&QA=&5# M;W!I97,@5$)?3F]N93$B#0HJ0VQO<V5523H@*D-87T,R1%]#;VQL871I;VX- M"@T**D]P96Y522`J0UA?0S)$7U-C86QE26UA9V4O26UA9V4@4V-A;&4Z(%!I M8VM/;F4-"BI/<F1E<D1E<&5N9&5N8WDZ(#(P($1O8W5M96YT4V5T=7`@*D-8 M7T,R1%]38V%L94EM86=E#0HJ1&5F875L=$-87T,R1%]38V%L94EM86=E.B!$ M96938V%L94EM86=E#0HJ0UA?0S)$7U-C86QE26UA9V4@1&5F4V-A;&5);6%G M92]0<FEN=&5R)W,@1&5F875L=#H@(B530TE04$0Z($1&12!38V%L94EM86=E M(%!R:6YT97(G<R(-"BI#6%]#,D1?4V-A;&5);6%G92!&:70R4&%P97(O1FET M('1O('!A&lt...

Hi all: There are hardwares that can do virtio datapath offloading while having its own control path. This path tries to implement a mdev based unified API to support using kernel virtio driver to drive those devices. This is done by introducing a new mdev transport for virtio (virtio_mdev) and register itself as a new kind of mdev driver. Then it provides a unified way for kernel virtio driver

Hi all: There are hardwares that can do virtio datapath offloading while having its own control path. This path tries to implement a mdev based unified API to support using kernel virtio driver to drive those devices. This is done by introducing a new mdev transport for virtio (virtio_mdev) and register itself as a new kind of mdev driver. Then it provides a unified way for kernel virtio driver