search for: nlists

Hi, I just observed a strange behavior in R. The rnorm function does not give me the numbers with a given length. I think it is somehow related to the internal representation of double-type numbers but I am not sure if this is supposed to happen. Below is a reproducible example ``` ## Create a list, we will only take the forth value, which is 0.6 nList <- seq(0,1,0.2) n <- nList[4] n # [1]

Hello gentlemen, I've discovered an interesting failure on some machine running 4.7. It's so weird so I'd very unlikely notice it at all, but thanks to top(1): when launched, instead of displaying some useful figures it exits with an error: "top: nlist failed". >From quick look it appears that kvm_nlist() returns NULL for nlst[0].n_type. Strange, ignoring; next exit point

Ubuntu 14.04, ctdb 2.5.3, samba 4.1.11. CTDB is working with IP takeover between the 2 nodes. The machine is joined to the domain. Any help with the following errors would be most gratefully received. 1. connect to socket error: ctdb status 2014/08/16 15:32:03.248034 [23255]: client/ctdb_client.c:267 Failed to connect client socket to daemon. Errno:Connection refused(111) common/cmdline.c:156

This is was something like a request for your comments, thoughts on the topic... Many of you will know that the "..." (aka \dots) argument is very useful for passing ``further graphical parameters'', but can be a pain when itself is passed to too many plotting functions inside your own function. An artificial example being myplot <- function(x,y, ...) { plot(0:1, 0:1,

Hi dear R-community, I wonder if anyone has written code that will post-process the results of a tapply to create a dataframe that includes the outcome, the factor by which the function has been applied, and, if the factor is also an interaction, then also the levels of contributing factors? >From this outcome <- tapply(data, A.B, function) I'd like to arrange something like this:

Dear All, My query is: Do we always need to use perl = TRUE option when doing ignore.case=TRUE? A small example : my_text = "RECOVERY OFFICER-II\nDEBTS RECOVERY TRIBUNAL-III\n RC No. 162/2015\nSBI VS RAMESH GUPTA.\n Dated: 01.03.2016 Item no.01\n Present: Ms. Sonakshi, the proxy counsel for Ms. Usha Singh, the counsel for ARCIL.\n None for the CDs.\n

Hi Nick, >> b) Further looking, there is a compiler attribute __attribute(used)__ which could be set for each symbol, but this is only a compiler hint. The information is not passed in the symbol table. If this is not passed in the symbol table to the linker, why is it in the DefinedAtom ? > In mach-o it *is* passed on to the linker by the compiler. It is the N_NO_DEAD_STRIP bit in the

Hi guys! I just try to compile Asterisk with "make all" and get the following lines multible times: cli.c:31:19: build.h: No such file or directory dlfcn.c:40:25: mach-o/dyld.h: No such file or directory dlfcn.c:41:26: mach-o/nlist.h: No such file or directory dlfcn.c:42:28: mach-o/getsect.h: No such file or directory Can someone tell me what's exactly missing?

On Nov 9, 2012, at 10:31 AM, Shankar Easwaran wrote: > Hi Nick, > > Dead stripping optimization needs a way to setup the roots which are live. The current code in Resolver does it by > > 1) setting all the global defined atoms to be the live set when building shared libraries (_options.allGlobalsAreDeadStripRoots) > 2) Or, uses a list of names that are dead strip roots (other

Hi All, I've added a very basic set of C bindings for OrcV2 in 633ea07200e, with an example in llvm/example/OrcV2Examples/BasicOrcV2CBindings. Development of the C APIs is being tracked by http://llvm.org/PR31103 -- if you're interested in C APIs for OrcV2 please get involved. I would especially appreciate feedback and patches from C API users: I don't have a use case for the C APIs

Hi Nick, Dead stripping optimization needs a way to setup the roots which are live. The current code in Resolver does it by 1) setting all the global defined atoms to be the live set when building shared libraries (_options.allGlobalsAreDeadStripRoots) 2) Or, uses a list of names that are dead strip roots (other types) Question:- *********** How are the dead strip root names supposed to be

Zitat von Ashim Kapoor <ashimkapoor at gmail.com>: > Dear All, > > My query is: > > Do we always need to use perl = TRUE option when doing ignore.case=TRUE? > > A small example : > > my_text = > "RECOVERY OFFICER-II\nDEBTS RECOVERY TRIBUNAL-III\n RC No. 162/2015\nSBI > VS RAMESH GUPTA.\n Dated: 01.03.2016 Item no.01\n > Present:

A few weeks ago I did a source upgrade from 6.2 to 7-STABLE. I didn't "make delete-old" so a bunch of old libraries and such were left lying around causing problems when I rebuilt all my ports. I'd read about some recent improvements to DDB and SCHED_ULE in 7-STABLE, and it's a miserable snowy weekend in Seattle right now, so I decided I'd take this opportunity to

Hi all, I've just migrated my mail system from procmail to managesieve/sieve and I'm having trouble trying to duplicate a could of rules I used to use in my procmail config. One particular rule would be this: :0 Wfh * ^Sender: owner-scientific-linux-devel at LISTSERV.FNAL.GOV | (sed -e '/^Subject:/ s/\[SCIENTIFIC-LINUX-DEVEL\] *//g'| sed ':a;N;$!ba;s/Precedence:

https://bugs.freedesktop.org/show_bug.cgi?id=34139 Summary: Seemingly random GUI lock-ups Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

This is probably a problem with having too many sections. There are a few places where mach-o has a limit on the number of sections. For instance the n_sect field of the nlist record is one byte. So any symbol in a section past the 255th section wraps around and shows up with the wrong n_sect number. -Nick On Apr 29, 2010, at 6:19 AM, Jack Howarth wrote: > I am wondering how the

Nick, Steven believes that aermod certainly could have more than 255 sections. Is there a particular approach that would be recommended for working around such a problem? Short of reducing the actual number of sections? It is suggested that this is why -ffunction-sections doesn't work on darwin and that one possible solution is to embed an 'ar' format section in the .gnu.lto

I am wondering how the following issue was handled for libLTO? We have a working patch to implement the FSF gcc LTO on darwin which now passes all of the liblto testsuite but are seeing linker issues with larger programs like aermod... as -arch x86_64 -force_cpusubtype_ALL -o aermod.o aermod.s /usr/bin/ld -dynamic -arch x86_64 -macosx_version_min 10.6.3 -weak_reference_mismatches

I looked into this further. ld64 has a macho_nlist abstraction over the various underlying nlist structures [1]. On x86-64, the P::getP referenced in n_value will resolve to [2], which in turn goes to [3], which calls OSReadLittleInt64. On a little endian machine, OSReadLittleEndian just calls _OSReadInt64 [4], which in turn does a pointer arithmetic and cast and then dereferences the pointer [5].

Then you need to rethink your data structure. Use a list instead of a data frame. The components of a list can have different lengths, and the "apply" family of functions (lapply(), etc.) can operate on them. Consult any good R tutorial for details. Cheers, Bert Bert Gunter "The trouble with having an open mind is that people keep coming along and sticking things into it."