search for: l24

...2 L16 7 0.714406779661017 33 L17 8 -2.28559322033898 34 L18 9 -3.78559322033898 35 L19 10 0.714406779661017 36 L21 13 -2.51016949152542 37 L22 14 0.489830508474576 38 L23 15 -2.03135593220339 39 L24 16 0.489830508474576 40 L25 17 0.489830508474576 41 L27 18 3.98983050847458 42 L28 19 0.489830508474576 43 L29 20 -3.51016949152542 44 L30 22 0.489830508474576 45 L1 1 -0.272561715904491 46 L2...

...DW_AT_decl_line (1) which does not contain DW_AT_Location. Currently, aarch64 does not emit DW_AT_Location for TLS variables. I could see at this line, it says some restriction in aarch64 elf abi. https://github.com/llvm-mirror/llvm/blob/master/lib/Target/AArch64/AArch64TargetObjectFile.cpp#L24 I would like to know community thoughts on this and is there any other way to tackle this, or we simply can not debug TLS variables for this architecture? ./Kamlesh -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attach...

...t is never freed? Wouldn't that result in actual leaks, since > OsinfoDb_t_finalize (g_object_unref'ing the OsinfoDb) wouldn't be > called? I was thinking because of this: https://github.com/libguestfs/virt-v2v/blob/cc294b7735dda467179b93a061d3631ac3547f26/v2v/libosinfo_utils.ml#L24 which IIUC will allocate a DB (on first access) but it is never released. (Note: I'm not saying this code is wrong) > > It could be that to express > > this properly we'd need to expose (db, os) tuples to the OCaml garbage > > collector. > > I thought about this,...

...pci-dss profile, ssg-centos7-xccdf.xml will always fail on test and remediation for disable_prelink rule. That seem to be caused by insufficient CentOS RPM customization of upstream code. Specifically this: https://github.com/OpenSCAP/scap-security-guide/blob/master/shared/oval/disable_prelink.xml#L24-L35 <https://github.com/OpenSCAP/scap-security-guide/blob/master/shared/oval/disable_prelink.xml> That condition will always fail on CentOS because it misses: <extend_definition comment="Installed OS is CentOS7" definition_ref=" installed_OS_is_centos7" /> I was th...

...ntain DW_AT_Location. >> >> Currently, aarch64 does not emit DW_AT_Location for TLS variables. >> I could see at this line, it says some restriction in aarch64 elf abi. >> >> https://github.com/llvm-mirror/llvm/blob/master/lib/Target/AArch64/AArch64TargetObjectFile.cpp#L24 >> >> I would like to know community thoughts on this and is there any other >> way to tackle this, or we simply can not debug TLS variables for this >> architecture? >> >> >> ./Kamlesh >> >> >> >> ___________________________________...

...ot; option for chain.c32. The correct segment parameter should be "seg=0x0F80", instead of the incorrect / failing ones "seg=0:0x8000:0x8100". References: https://svn.reactos.org/svn/reactos/trunk/reactos/boot/freeldr/notes.txt?revision=73859&view=markup&pathrev=73859#l24 https://git.reactos.org/?p=reactos.git;a=blob;f=reactos/boot/freeldr/notes.txt;hb=HEAD https://git.reactos.org/?p=reactos.git&a=search&h=HEAD&st=grep&s=FREELDR_BASE https://git.reactos.org/?p=reactos.git;a=blob;f=reactos/boot/freeldr/freeldr/include/arch/pc/x86common.h;h=c7...

...g to newer/current versions of Reactos. The updated segment parameter should be "seg=0x0F80", instead of the older ones "seg=0:0x8000:0x8100". References: https://svn.reactos.org/svn/reactos/trunk/reactos/boot/freeldr/notes.txt?revision=73859&view=markup&pathrev=73859#l24 https://git.reactos.org/?p=reactos.git;a=blob;f=reactos/boot/freeldr/notes.txt;hb=HEAD https://git.reactos.org/?p=reactos.git&a=search&h=HEAD&st=grep&s=FREELDR_BASE https://git.reactos.org/?p=reactos.git;a=blob;f=reactos/boot/freeldr/freeldr/include/arch/pc/x86common.h;h=c7...

Dear libguestfs developers, as explained yesterday by Ubuntu guys on my bug report https://bugs.launchpad.net/ubuntu/+source/libguestfs/+bug/1722800 the libguestfs currently supports ZFS filesystem only partially i.e. for virt-rescue. Q: Would it be possible to bring ZFS support also to other libguestfs utils, like guestfish and virt-format? I would need to have two usecases supported: a)

Hello, I''m writing my first puppet function rspec test and am having a problem which I don''t see how to solve. The function (and the test) involve access to files through the File Server. In order for the function (and the test) to work I need to pass "--fileserverconf=fileserver.conf" parameter to Puppet. So far I haven''t found a way to do that. If I

I''m trying to create a function that I can call in a manifest like this: $doc = doc(''apache::service'') In the function, I want it to actually find the filename for the ''apache::service'' class... from there, I''m going to run some code that will generate the puppet-doc in text format, and then return it in a variable. Ultimately this is so

...stfs/blob/master/daemon/mkfs.c#L35 > b) manage files from ZFS volume (read, write) I believe that mounting a ZFS volume should just work currently. If not, you might need to make only simple adjustments to the mount API: https://github.com/libguestfs/libguestfs/blob/master/daemon/mount.ml#L24 This should allow you to read and write files. Providing full ZFS volume management is a quite a bit harder. It would involve pulling in some of the zfs APIs and turning them into libguestfs APIs. There is lots of documentation about how to add new APIs here: http://libguestfs.org/guestfs-ha...

...that result in actual leaks, since > > OsinfoDb_t_finalize (g_object_unref'ing the OsinfoDb) wouldn't be > > called? > > I was thinking because of this: > > https://github.com/libguestfs/virt-v2v/blob/cc294b7735dda467179b93a061d3631ac3547f26/v2v/libosinfo_utils.ml#L24 > > which IIUC will allocate a DB (on first access) but it is never > released. Oh this is interesting. I read in the documentation that custom blocks have tag Custom_tag, which is higher than No_scan_tag, and thus they aren't scanned by the GC. Indeed, even trying to Gc.finalize on...

...e, ssg-centos7-xccdf.xml will always fail > on test and remediation for disable_prelink rule. That seem to be caused by > insufficient CentOS RPM customization of upstream code. Specifically this: > https://github.com/OpenSCAP/scap-security-guide/blob/master/shared/oval/disable_prelink.xml#L24-L35 > <https://github.com/OpenSCAP/scap-security-guide/blob/master/shared/oval/disable_prelink.xml> > > That condition will always fail on CentOS because it misses: > <extend_definition comment="Installed OS is CentOS7" definition_ref=" > installed_OS_is_cent...

Hi all ! I can''t seem to make a simple thing work... The code is here: http://pastie.caboo.se/130660 Essentially, that''s a form with a couple of partials. The backtrace is included in the pastie. It looks like the context for the current view is lost when a partial is rendered. In _series.html.erb:2, I use "series" to get the name. This is the parameter I

...t; > The correct segment parameter should be "seg=0x0F80", > instead of the incorrect / failing ones "seg=0:0x8000:0x8100". > > References: > https://svn.reactos.org/svn/reactos/trunk/reactos/boot/freeldr/notes.txt?revision=73859&view=markup&pathrev=73859#l24 > > https://git.reactos.org/?p=reactos.git;a=blob;f=reactos/boot/freeldr/notes.txt;hb=HEAD > > https://git.reactos.org/?p=reactos.git&a=search&h=HEAD&st=grep&s=FREELDR_BASE > > https://git.reactos.org/?p=reactos.git;a=blob;f=reactos/boot/freeldr/freeldr/include/...

...o> void foo(); void qux(); struct A { ~A() { try { throw 0; } catch (double) { printf("hoo\n"); } } }; void bar() { try { A a; foo(); } catch (const char *c) { printf("hello world! %s\n", c); } } The cleanup part for the "foo" call has this: L24: # basic block 4 L3: movl %edx, %ebx movq %rax, %r13 movl $4, %edi call ___cxa_allocate_exception movq %rax, %rdi movl $0, (%rax) movq __ZTIi at GOTPCREL(%rip), %rsi xorl %edx, %edx LEHB2: call...

Hi Pino: I've suppressed some OCaml and libosinfo valgrind errors in virt-v2v. The remaining valgrind errors are here: http://oirase.annexia.org/tmp/v2vvg/ They all seem to be basically the same. But I couldn't work out if these are expected leaks in the libosinfo code (in which case we should suppress them), or if they are actual bugs because we are missing a true destructor here:

...el %CF237 CF237: ; preds = %CF237, %CF271, %CF268, %CF251 %Sl22 = select i1 true, i16 -1, i16 %E6 %Cmp23 = icmp sgt i1 %E13, true br i1 %Cmp23, label %CF237, label %CF256 CF256: ; preds = %CF256, %CF237 %L24 = load i64, i64* %A store i64 %L5, i64* %Sl17 %E25 = extractelement <4 x i16> zeroinitializer, i32 3 %Shuff26 = shufflevector <4 x i16> %Shuff7, <4 x i16> zeroinitializer, <4 x i32> <i32 2, i32 4, i32 6, i32 undef> %I27 = insertelement <4 x i16> zeroiniti...

...`````````'@`=#@$````6 M````1G5N;GD@8V%C:&EN9R!P<F]B;&5M````'@`U$`$```!`````/#<Q,3,T M-$,S,4%#1$0Q,3$X0CDT,#`V,#DW.#(W1#5",#4W,#@S0&5X8VAA;F=E+FYE M8W1E8V@N8V\N=6L^``L`*0``````"P`C```````#``80%.Q4CP,`!Q`>`P`` M`P`0$``````#`!$0`````!X`"!`!````90```$A)1D],2U,L24%-15A015)) M14Y#24Y'05-44D%.1T504D]"3$5-5TE42#$Y,3A0-T].1E)%14)31#(R,E=( M14Y)04-#15-31DE,15-&4D]-5$A%2$]-15-32$%212Q-65=)3CD``````@%_ M``$```!`````/#<Q,3,T-$,S,4%#1$0Q,3$X0CDT,#`V,#DW.#(W1#5",#4W >,#@S0&5X8VAA;F=E+FYE8W1E8V@N8V\N=6L^``;3 ` end

...you divorce the point where you branch to the catch handler from the point where it throws, you now have a huge gap that cannot be easily recovered from, and may be impossible to recover from. This is the code that G++ generates from the example in my proposal: LEHB2: call __Z3foov LEHE2: . . . L24: # basic block 10 movq %rax, %r12 L5: # basic block 11 movl %edx, %ebx leaq -18(%rbp), %rdi call __ZN1BD1Ev movslq %ebx,%rdx jmp L7 . . . L7: # basic block 15 movl %edx, %ebx leaq -17(%rbp), %rdi call __ZN1AD1Ev movslq %ebx,%rdx jmp L19 . . . L19: # basic block 19 cmpq $3, %rdx je...