search for: 14140

Full_Name: Raimar Falke Version: R version 2.10.0 (2009-10-26) OS: Linux 2.6.27-16-generic #1 SMP Tue Dec 1 19:26:23 UTC 2009 x86_64 GNU/Linux Submission from: (NULL) (134.102.222.56) The construction of a data frame in the way shown below requires much more memory than expected. If we assume a cell value takes 8 bytes the total amount of the data is 128mb. However the process takes about

...on to the next method using callGeneric again. Arguments are passed. Now this all works smoothly, as long as you stay in the global environment : require(raster) a <- raster() a[] <- 1:ncell(a) origin <- c(-80,50) eff.dist <- 100000 unlist(xyValues(a,xy=origin,buffer=eff.dist)) [1] 14140 14141 14500 14501 Now let's make a very basic test function : test <- function(x,orig.point){ eff.distance <- 100000 p <- unlist(xyValues(x,xy=orig.point,buffer=eff.distance)) return(p) } This gives the following result : > test(a,origin) Error in .local(object, xy, ....

...erroring because the index is out of range. > > Either: > 1) The binary is corrupt. You can check that by running: > dyldinfo -lazy_bind to see the lazy pointers Nick, I attached dragonegg_so_lazy_bind.txt and LLVMPolly_so_lazy_bind.txt to http://llvm.org/bugs/show_bug.cgi?id=14140. Is there anything significant in those lists of lazy pointers relative to the failure we are seeing? FYI, I see the same failure for both x86_64-apple-darwin11 and x86_64-apple-darwin12 with current llvm/polly/dragonegg svn using Xcode 4.5.1's linker. > or > 2) Something else is wrong w...

...of range. > > > > Either: > > 1) The binary is corrupt. You can check that by running: > > dyldinfo -lazy_bind to see the lazy pointers > > Nick, > I attached dragonegg_so_lazy_bind.txt and LLVMPolly_so_lazy_bind.txt to http://llvm.org/bugs/show_bug.cgi?id=14140. > Is there anything significant in those lists of lazy pointers relative to the failure we are seeing? FYI, I see the same > failure for both x86_64-apple-darwin11 and x86_64-apple-darwin12 with current llvm/polly/dragonegg svn using Xcode 4.5.1's > linker. > > > or > &gt...

...from blundering into SMB1-specific calls. o Ralph Boehme <slow at samba.org> * BUG 14137: Fix stale file handle error when using mkstemp on a share. o Isaac Boukris <iboukris at gmail.com> * BUG 14106: Fix spnego fallback from kerberos to ntlmssp in smbd server. * BUG 14140: Overlinking libreplace against librt and pthread against every binary or library causes issues. o G?nther Deschner <gd at samba.org> * BUG 14130: s3-winbindd: Fix forest trusts with additional trust attributes. * BUG 14134: auth/gensec: Fix non-AES schannel seal. o Amitay Isaa...

...from blundering into SMB1-specific calls. o Ralph Boehme <slow at samba.org> * BUG 14137: Fix stale file handle error when using mkstemp on a share. o Isaac Boukris <iboukris at gmail.com> * BUG 14106: Fix spnego fallback from kerberos to ntlmssp in smbd server. * BUG 14140: Overlinking libreplace against librt and pthread against every binary or library causes issues. o G?nther Deschner <gd at samba.org> * BUG 14130: s3-winbindd: Fix forest trusts with additional trust attributes. * BUG 14134: auth/gensec: Fix non-AES schannel seal. o Amitay Isaa...

...vfs_glusterfs: Use pthreadpool for scheduling aio operations. o Aaron Haslett <aaronhaslett at catalyst.net.nz> * BUG 13977: ldb: baseinfo pack format check on init. * BUG 13978: ldb: ldbdump key and pack format version comments. o Amitay Isaacs <amitay at gmail.com> * BUG 14140: Overlinking libreplace against librt and pthread against every binary or library causes issues. * BUG 14147: ctdb-vacuum: Process all records not deleted on a remote node. o Bj?rn Jacke <bj at sernet.de> * BUG 14136: classicupgrade: Fix uncaught exception. * BUG 14139: fault....

...vfs_glusterfs: Use pthreadpool for scheduling aio operations. o Aaron Haslett <aaronhaslett at catalyst.net.nz> * BUG 13977: ldb: baseinfo pack format check on init. * BUG 13978: ldb: ldbdump key and pack format version comments. o Amitay Isaacs <amitay at gmail.com> * BUG 14140: Overlinking libreplace against librt and pthread against every binary or library causes issues. * BUG 14147: ctdb-vacuum: Process all records not deleted on a remote node. o Bj?rn Jacke <bj at sernet.de> * BUG 14136: classicupgrade: Fix uncaught exception. * BUG 14139: fault....

...ource if appropriate. >> See <http://gcc.gnu.org/bugs.html> for instructions. >> >> I'll open a bugzilla for this one. > > Yes, please do. This is an interesting problem. I have no solution of > the top of my head. Done... http://llvm.org/bugs/show_bug.cgi?id=14140. I'll ping the MacPorts maintainers of their llvm-3.2 package to update it to contain polly as well. This, with a rebuild of their dragonegg-3.2 package, should provide the Apple programmers with pre-built binaries to debug this issue without tainting themselves with GPLv3 code. Can you take a...

...iback.hide=(0a:01.0) --- After that, I see the PCI in domU: ~# lspci 00:00.0 ISDN controller: GmbH ISDN network Controller [HFC-4S] (rev 01) -- PROBLEM -- My first problem is that dom0 and domU share IRQ 18: ** dom0 ** ~# cat /proc/interrupts CPU0 CPU1 18: 14140 0 Phys-irq uhci_hcd:usb3 ** domU ** ~# cat /proc/interrupts CPU0 18: 16507 Phys-irq HFC-multi Obviously, the interrupts so big number by IRQ18 in dom0 is "false", they are in fact interruptions of the HFC card in domU. If I reboot or de...

...er: >>>> 1) The binary is corrupt. You can check that by running: >>>> dyldinfo -lazy_bind to see the lazy pointers >>> >>> Nick, >>> I attached dragonegg_so_lazy_bind.txt and LLVMPolly_so_lazy_bind.txt to http://llvm.org/bugs/show_bug.cgi?id=14140. >>> Is there anything significant in those lists of lazy pointers relative to the failure we are seeing? FYI, I see the same >>> failure for both x86_64-apple-darwin11 and x86_64-apple-darwin12 with current llvm/polly/dragonegg svn using Xcode 4.5.1's >>> linker. &gt...

...rg/bugs.html> for instructions. >>>> >>>> I'll open a bugzilla for this one. >>> >>> Yes, please do. This is an interesting problem. I have no solution of >>> the top of my head. >> >> Done... http://llvm.org/bugs/show_bug.cgi?id=14140. I'll ping the MacPorts maintainers of their llvm-3.2 package to update >> it to contain polly as well. This, with a rebuild of their dragonegg-3.2 package, should provide the Apple programmers with >> pre-built binaries to debug this issue without tainting themselves with GPLv3 cod...

...gt; See <http://gcc.gnu.org/bugs.html> for instructions. >>> >>> I'll open a bugzilla for this one. >> >> Yes, please do. This is an interesting problem. I have no solution of >> the top of my head. > > Done... http://llvm.org/bugs/show_bug.cgi?id=14140. I'll ping the MacPorts maintainers of their llvm-3.2 package to update > it to contain polly as well. This, with a rebuild of their dragonegg-3.2 package, should provide the Apple programmers with > pre-built binaries to debug this issue without tainting themselves with GPLv3 code. Than...

...t; >>> Either: >>> 1) The binary is corrupt. You can check that by running: >>> dyldinfo -lazy_bind to see the lazy pointers >> >> Nick, >> I attached dragonegg_so_lazy_bind.txt and LLVMPolly_so_lazy_bind.txt to http://llvm.org/bugs/show_bug.cgi?id=14140. >> Is there anything significant in those lists of lazy pointers relative to the failure we are seeing? FYI, I see the same >> failure for both x86_64-apple-darwin11 and x86_64-apple-darwin12 with current llvm/polly/dragonegg svn using Xcode 4.5.1's >> linker. >> >&...

...0/4.7.2/cc1 Program received signal SIGTRAP, Trace/breakpoint trap. 0x00007fff5fc0109d in __dyld_dyld_fatal_error () where all of the bindings from LLVMPolly.so occur before the initializer function is called. Was this behavior expected? Also, as I noted on http://llvm.org/bugs/show_bug.cgi?id=14140#c13, a static build of LLVMPolly.so on 10.6 exhibits the same dyld error. Am I correct to assume that test proves that the offending symbol can't be from libcloog-isl, libisl, libgmp or libstdc++ because, when statically linked, those symbols can't be obtained from cc1? Is it vaild to assum...

On Oct 22, 2012, at 11:34 AM, Jack Howarth wrote: > Nick, > I have uploaded the full walk with 'set env DYLD_PRINT_INITIALIZERS'. It didn't seem very informative > as the dyld error occurs right after... > > (gdb) > llvm::sys::DynamicLibrary::getPermanentLibrary (filename=0x142903da8 "/sw/opt/llvm-3.2/lib/LLVMPolly.so", errMsg=0x7fff5fbfe6e0) at

...> >>>> > >>>> I'll open a bugzilla for this one. > >>> > >>> Yes, please do. This is an interesting problem. I have no solution of > >>> the top of my head. > >> > >> Done... http://llvm.org/bugs/show_bug.cgi?id=14140. I'll ping the MacPorts maintainers of their llvm-3.2 package to update > >> it to contain polly as well. This, with a rebuild of their dragonegg-3.2 package, should provide the Apple programmers with > >> pre-built binaries to debug this issue without tainting themselves with...

...eived signal SIGTRAP, Trace/breakpoint trap. > 0x00007fff5fc0109d in __dyld_dyld_fatal_error () > > where all of the bindings from LLVMPolly.so occur before the initializer function is called. Was this behavior > expected? > Also, as I noted on http://llvm.org/bugs/show_bug.cgi?id=14140#c13, a static build of LLVMPolly.so on 10.6 exhibits the > same dyld error. Am I correct to assume that test proves that the offending symbol can't be from libcloog-isl, libisl, > libgmp or libstdc++ because, when statically linked, those symbols can't be obtained from cc1? Is it vail...

Hi *, I''d like to know from users of the Account location plugin if it works with webrick without adding all the subdomains to /etc/hosts. I''m on OS X. I would also be glad to hear experiences using this plugin. ngw -- Nicholas Wieland nicholas_wieland@yahoo.it Chiacchiera con i tuoi amici in tempo reale!

...GE_FILES conftest.c 1>&5 configure:14134: checking whether struct passwd has pw_comment configure:14147: gcc -c -O -D_LARGE_FILES conftest.c 1>&5 configure: In function `main': configure:14143: structure has no member named `pw_comment' configure: failed program was: #line 14140 "configure" #include "confdefs.h" #include <pwd.h> int main() { struct passwd p; p.pw_comment; ; return 0; } Even though I found it I can't tell if it got enabled or not. Because of the problems I'm having I'm assuming that it didn't get enabled. Does a...