search for: cset

...F0EB: Rf_eval (eval.c:461) ==32503== by 0x8160DA7: do_begin (eval.c:1174) ==32503== by 0x815F0EB: Rf_eval (eval.c:461) ==32503== by 0x8162210: Rf_applyClosure (eval.c:667) The leaked blocks are allocated in iinternal_function build_range_exp() at 5200 /* Use realloc since mbcset->range_starts and mbcset->range_ends 5201 are NULL if *range_alloc == 0. */ 5202 new_array_start = re_realloc (mbcset->range_starts, wchar_t, 5203 new_nranges); 5204 new_array_end = re_realloc (mb...

...still reachable: 12,599,585 bytes in 5,915 blocks. ==28643== suppressed: 0 bytes in 0 blocks. ==28643== Reachable blocks (those to which a pointer was found) are not shown. ==28643== To see them, rerun with: --show-reachable=yes The flagged memory block is the range_ends component of mbcset. I think that range_starts was also being leaked, but valgrind was combining the two. It looks like the cpp macro _LIBC is not defined when I compile R in this Linux box. regex.c defines range_ends and range_starts as different types, depending on the value of _LIBC, and it allocates space for t...

Hi Keir, The changeset 18473 on xen-unstable needs to be back-ported to xen-3.3 tree. Because the gdbstub.c file isn't modified in xen-3.3 tree, the effort involved would be trival. Thanks. -- Guanqun _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...the sets package yesterday, which seems to be a very powerful package: thanks to the developers. I wanted to define sets of lists where 2 lists are considered equal if they have the same length. So, I implemented: match.2.list <- function(l1,l2){ length(l1)==length(l2) } and then defined my cset as: s <- set(list(1,2),list(3,4)) lset <- cset(s,matchfun(match.2.list)) so if I now do: y <- list(3,4) y %e% lset I get the correct answer, which is TRUE. But if I do: x <- list(1,8) x %e% lset I now get FALSE, even though x is a list of length 2, and should thus match any of the...

...599,585 bytes in 5,915 blocks. > ==28643== suppressed: 0 bytes in 0 blocks. > ==28643== Reachable blocks (those to which a pointer was found) are not shown. > ==28643== To see them, rerun with: --show-reachable=yes > > The flagged memory block is the range_ends component of mbcset. > I think that range_starts was also being leaked, but valgrind was > combining the two. > > It looks like the cpp macro _LIBC is not defined when I compile > R in this Linux box. regex.c defines range_ends and range_starts > as different types, depending on the value of _LIBC,...

Hi all. I have pushed my earlier announced kbuild improvements patch to: bk://linux-sam.bkbits.net/2.5-klibc First cset is the earlier posted cset, whit a few small modifications. One important change is that the usr/Makefile now uses *.a files in initramfs-y assignment. I realised that the purpose was to express what kinit were using / referring. Second cset is a trivial cset that just move USER* definitions to Ma...

We have tested Xen for 3.0.3rc1. The test includes Guest installation, device model, control panel, guest os and basic function tests. Here are issues found in our tests, For the first 6 issues, I think it''s better to be fixed in 3.0.3: 1. Para-virtualization driver doen''t work for HVM guests The hvm guest always hanged or met kernel panic when trying to load xenbus.ko. So vbd

Hi all, All nightly cases can pass today. Old issues : ================================================= 1).time latency is a negative number on window guest when vcpu > 1          http://otc-qa.sh.intel.com/xen/bugzilla/show_bug.cgi?id=991 2) Can not install 32bit Fedora 7 with vcpu > 1 http://otc-qa.sh.intel.com/xen/bugzilla/show_bug.cgi?id=1154 Testing environments:

Hi all, There are two issues have been fixed in this changeset. It seems there is only one major issue in nightly testing. Fixed issue: ================================================= 1) HVM domain can not boot up if provide both "xvda" (no bootable OS) and "hda". 2) Can not boot up 2.6.23 kernel when acpi=1         

Hi all, This is today''s xen nightly test report, changeset: 16281 unstable tree.  Linux-xen:297 One new issue on 32E, can not insmod "xen-platform-pci.ko",see the issue list. One new issue on PAE, can not boot up win2K guest, see the issue list. Other failed cases can pass manually. New issues: ================================================= 1) cannot insert module

Hi, 1 issue has been fixed: PV driver can not be inserted on IA32 PAE Guest. On PAE, 2.6.23 kernel HVM Linux will boot failed if set acpi=1. SMP Fedora 7 can not be installed. On IA32E, Local live migration and save&restore can not work. New issue: ================================================= 1) Can not install 32bit Fedora 7 with vcpu > 1 (This issue is not because latest

Hi all, This is today''s xen nightly test report against Xen cset: #16475 (unstable tree) && Dom0: #323 In the new testing, we found 2 new issues: Dom0''s time is not correct after S3, and PV dirver can not build with RHEL5 kernel. New issue : ================================================= 1) PV drivers can not build with RHEL5 kenrel. When...

Hello, Thanks James for the reply. That cleared a few things out. Apologies for replying late because of exams going on. I was going through the previous clustering API to understand how it worked and it seems like the the approach for construction of the termlists which are used for distance metrics use TF-IDF weighting with cosine similarity, which is very similar to the approach I would need

...ettingStarted.html, gcc 3.4.2 should be used but I don't know if this document is up to date regarding the required software versions) Anyway I also tried with gcc version 3.4.6 (Ubuntu 3.4.6-6ubuntu5) And now, I get a bunch of errors like this one: llvm-2.9/lib/Support/regcomp.c: In function `cset* allocset(parse*)': llvm-2.9/lib/Support/regcomp.c:1050: error: invalid conversion from `void*' to `cset*' llvm-2.9/lib/Support/regcomp.c:1055: error: invalid conversion from `void*' to `uch*' llvm-2.9/lib/Support/regcomp.c: In function `void mcadd(parse*, cset*, const char*)...

I tried on a different machine x86_64 ( vs x86 ) and I don't have these issues anymore (the tests are failing on the x86 machine because of a segmentation fault) Both builds were done using: g++ (GCC) 4.2.4 (Ubuntu 4.2.4-1ubuntu4) Something should be wrong with my environment... The only differences I noticed during the compilation are the following warnings (which appear several times, but

...d this device and can not find device > > driver associate with it. > > > > To verify this just revert the patches of changset 11161/11160 > > We are working on the fix now, revert patch is not the solution > > anyway... > I just tried this, and as far as I can see cset 11161 doesn''t make any > difference to the behaviour, while 11160 is fairly obviously > irrelevant to this kind of thing. > > With or without 11161, I see guests crashing with > > (XEN) sh error: sh_page_fault__shadow_3_guest_2(): disabled-APIC access: > not supporte...

.../usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/cmap.cc /usr_plus/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/color.cc /usr_plus/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/cset.cc /usr_plus/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/device.cc /usr_plus/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/groff/src/libs/libgroff/errarg.cc /usr_plus/src/gnu/usr.bin/groff/src/libs/libgroff/../../../../../../contrib/...

Hi, On paravirt x86 (both 32- and 64-bit), since cset 13998: http://xenbits.xensource.com/xen-unstable.hg?rev/13998 we translate all ptes from being mfn-based to pfn-based when the hardware _PAGE_PRESENT bit is cleared. We do this for PROT_NONE pages, which appear to the HV to be non-present, but which are special-cased in the kerne...

Hi all, We have done the ABAT test to Xen3.3.0-rc4 (staging#18314) on IA64. No issue was found for IPF. Thanks! Detail Xen/IA64 Unstable Cset #18314 Status Report ============================================================ Test Result Summary: # total case: 17 # passed case: 17 # failed case: 0 ============================================================ Testing Environment: platform: Tiger4 p...

...o construct sets of S4 objects? It seems the constructor set does not like it: Error in as.vector(x, "character") : cannot coerce type 'environment' to vector of type 'character' Regards Johnny PS: by the way, does anyone know where I can find some examples using the cset class from the "sets" package, beside the one in the standard doc? [[alternative HTML version deleted]]