search for: nlist

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 is: "top: kvm_read for _ccpu: Bad address" Something bad happens: kernel virtual memory symbol table becomes unreadable, so kvm calls fail... But system runs a...

...le netbios = Yes clustering = Yes ctdbd socket = /usr/local/var/run/ctdb/ctdbd.socket [users] path = /cluster/users read only = No ************** /etc/ctdb/50.samba ps aux|grep ctdbd root 25902 3.3 3.6 26772 18460 ? SLs 15:38 0:08 /usr/sbin/ctdbd --pidfile=/var/run/ctdb/ctdbd.pid --nlist=/etc/ctdb/nodes --socket=/usr/local/var/run/ctdb/ctdbd.socket --public-addresses=/etc/ctdb/public_addresses -d NOTICE --syslog root 25904 0.0 0.0 3012 396 ? S 15:38 0:00 /usr/sbin/ctdbd --pidfile=/var/run/ctdb/ctdbd.pid --nlist=/etc/ctdb/nodes --socket=/usr/local/var/run/ctdb/ct...

...that I can pass "..." down to other functions which would want to see a `myarg' argument. Something like if("myarg" %in% (naml <- names(list(...)))) { ## ok, it's there, take it out marg <- list(...)$ marg ## what I now would like is ... <- unlist( list(...)["myarg" != naml] ) } BTW: one relatively ugly workaround is to use the above *list* say nlist <- list(...)["myarg" != naml] and do all subsequent call where I'd had "..." as do.call( <funname> , c(list( <<other args to f...

...c(rep("B",4), rep("A",4))) y <- factor(c(1,2,1,2,1,2,1,2)) z <- rnorm(8) data <- as.data.frame(cbind(x, y, z)) data$x.y <- interaction(x,y) my.test <- tapply(data$z, data$x.y, mean) test <- as.data.frame(as.numeric(my.test)) names(test) <- "Mean" nList <- function(list, n) list[[n]] test$x <- factor(as.character(lapply(strsplit(row.names(my.test), "\\."), nList, n=1))) test$y <- factor(as.character(lapply(strsplit(row.names(my.test), &...

...nThe proxy counsel for CHFI further requested to issue demand notice thereby mentioning the name of ARCIL. Request allowed.\nRegistry is directed to issue fresh demand notice mentioning the name of ARCIL.\nCHFI is directed to file status of the mortgaged property as well as other assets of the CDs.\nList the case on 28.03.2016.\n (SUJEET KUMAR)\nRECOVERY OFFICER-II." My regular expression is: parties_present_start_1= regexpr("\n.*Present.*\n.*\n",my_text,ignore.case=TRUE,perl=T) parties_present_start_2= regexpr("\n.*Present.*\n.*\n",my_text,ignore.case=TRUE) > parti...

...bol, 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 n_desc field of the nlist struct. Are you saying that that information is not recorded in ELF .o files? On ELF x86_64, I dont see the information being passed. Is clang planning to add this support ? Thanks Shankar Easwaran -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by the Linux Found...

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? Regards from Munich Julian

...h 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 n_desc field of the nlist struct. Are you saying that that information is not recorded in ELF .o files? -Nick

...Tuesday this week. LLJIT now enables exception handling for MachO by default (7266a8bfeb8). RuntimeDyldCOFF will now build stubs for dllimports (337e131ca7de). JITLink now correctly scopes MachO linker-private symbols (b64afadf306, 9c9eb60b4b), and reads the 'weak' flag from the correct nlist field (c700e0317c2). Stackmaps and DWARF can now be used in the same file without triggering an assertion (3f981cdde90f). -- Lang. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200315/308f1439/attachment....

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

...or > CHFI further requested to issue demand notice thereby mentioning the name > of ARCIL. Request allowed.\nRegistry is directed to issue fresh demand > notice mentioning the name of ARCIL.\nCHFI is directed to file status of > the mortgaged property as well as other assets of the CDs.\nList the case > on 28.03.2016.\n (SUJEET KUMAR)\nRECOVERY OFFICER-II." > > My regular expression is: > > parties_present_start_1= > regexpr("\n.*Present.*\n.*\n",my_text,ignore.case=TRUE,perl=T) > > parties_present_start_2= > regexpr("\n.*Present.*\n.*\n&q...

...E, and it's a miserable snowy weekend in Seattle right now, so I decided I'd take this opportunity to update my system to the latest 7-STABLE and get rid of those old libraries properly this time. Now sysutils/wmmemmon and sysutils/wmcpuload stopped working. Both die with: kvm_open: kvm_nlist: No such file or directory error extracting symbols I found two PRs for other ports (ascpu and wmcube-gdk) to fix similar problems, but they seem to be related to 8-CURRENT. The solution in both of these cases is to use sysctls instead of using kvm. PR numbers are 119923 and 120142. My questio...

...ying 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: list/Precedence: list\nList-Post: <mailto:scientific-linux-devel at fnal.gov>/g') :0 A .Mail\ Lists.SL-Devel/ This in effect adds the header "List-Post: <mailto:scientific-linux-devel at fnal.gov>" after "Precedence: list". This allows me to use the Reply To List functionality in Thunde...

...t=0x7fff285bab60) at exa_accel.c:817 #11 0x00000000004d7c17 in damagePolyFillRect (pDrawable=0x1d58f20, pGC=0x100c1a0, nRects=1, pRects=0x7fff285bab60) at damage.c:1400 #12 0x00007fcc4956a398 in exaGlyphs (op=3 '\003', pSrc=0x1bae0d0, pDst=0x1cb8000, maskFormat=0xfb0e88, xSrc=665, ySrc=354, nlist=1, list=0x7fff285bb540, glyphs=0x7fff285bad40) at exa_glyphs.c:785 #13 0x00000000004d7315 in damageGlyphs (op=3 '\003', pSrc=0x1bae0d0, pDst=0x1cb8000, maskFormat=0xfb0e88, xSrc=665, ySrc=354, nlist=1, list=0x7fff285bb540, glyphs=0x7fff285bad40) at damage.c:718 #14 0x00000000004d0c6...

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 following issue was handled for > libLTO? We have a working patch to implement th...

...he limited object format can be avoided. Jack On Thu, Apr 29, 2010 at 10:06:00PM -0700, Nick Kledzik wrote: > 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 following issue was handled for > > libLTO? We h...

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 arithmet...

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."

...some of the symbols present in my binary (memory allocator, mmap). Interposition support is somewhat lacking in the Mach-O toolchain and runtime linker despite the Mach-O format technically supporting what I need (N_INDR and N_WEAK_DEF). > > - https://developer.apple.com/documentation/kernel/nlist_64 <https://developer.apple.com/documentation/kernel/nlist_64> Dyld does not generally use nlists at runtime except for things like dladdr(), and has not for the last 10 years or so. Instead dyld uses a trie to publish exports, and and a small byte code language to describe binding imports. W...