search for: pargs

Displaying 15 results from an estimated 15 matches for "pargs".

Did you mean: args
2002 Jun 12
3
help debugging segfaults
...5 PROTECT(ans = allocVector(VECSXP, nargs)); 1846 havenames = 0; 1847 if (dup) { 1849 info.cargs = cargs; 1850 info.allArgs = args; 1851 info.nargs = nargs; 1852 info.functionName = buf; 1853 nargs = 0; 1854 for (pargs = args ; pargs != R_NilValue ; pargs = CDR(pargs)) { 1855 if(argConverters[nargs]) { 1864 PROTECT(s = CPtrToRObj(cargs[nargs], CAR(pargs), which)); Program received signal SIGSEGV, Segmentation fault. 0x080ddc6a in RunGenCollect (size_needed=1515400) at memory.c:1...
2002 Jun 12
3
help debugging segfaults
...5 PROTECT(ans = allocVector(VECSXP, nargs)); 1846 havenames = 0; 1847 if (dup) { 1849 info.cargs = cargs; 1850 info.allArgs = args; 1851 info.nargs = nargs; 1852 info.functionName = buf; 1853 nargs = 0; 1854 for (pargs = args ; pargs != R_NilValue ; pargs = CDR(pargs)) { 1855 if(argConverters[nargs]) { 1864 PROTECT(s = CPtrToRObj(cargs[nargs], CAR(pargs), which)); Program received signal SIGSEGV, Segmentation fault. 0x080ddc6a in RunGenCollect (size_needed=1515400) at memory.c:1...
2002 Jun 18
1
can't find array overruns (was: help debugging segfaults)
...P, nargs)); > 1846 havenames = 0; > 1847 if (dup) { > 1849 info.cargs = cargs; > 1850 info.allArgs = args; > 1851 info.nargs = nargs; > 1852 info.functionName = buf; > 1853 nargs = 0; > 1854 for (pargs = args ; pargs != R_NilValue ; pargs = > CDR(pargs)) { > 1855 if(argConverters[nargs]) { > 1864 PROTECT(s = CPtrToRObj(cargs[nargs], > CAR(pargs), > which)); > > Program received signal SIGSEGV, Segmentation fault. > 0x080ddc6a in RunGenCo...
2008 Feb 13
3
[LLVMdev] LLVM2.2 x64 JIT trouble on VStudio build
Hola LLVMers, I'm debugging through some strangeness that I'm seeing on X64 on windows with LLVM2.2. I had to change the code so that it would engage the x64 target machine on windows builds, but I've otherwise left LLVM 2.2 alone. The basic idea is that I've got a function bar which is compiled by VStudio and I'm creating another function foo via LLVM JIT which is going
2003 Feb 10
2
Wireframe (lattice) questions
I have a few questions on formatting wireframe plots: 1. How can I remove (or at least "white-out") the border on the plot? (I.e., the 2-d box around the whole plotting area, not the 3-d cube). I'm willing to hack the code if necessary. 2. Is it possible to suppress plotting of all sides of the cube except for the axes? 3. Is there a reliable way to print expressions in
2008 Feb 15
0
[LLVMdev] LLVM2.2 x64 JIT trouble on VStudio build
On Feb 12, 2008, at 5:26 PM, Chuck Rose III wrote: > Hola LLVMers, > > I’m debugging through some strangeness that I’m seeing on X64 on > windows with LLVM2.2. I had to change the code so that it would > engage the x64 target machine on windows builds, but I’ve otherwise > left LLVM 2.2 alone. The basic idea is that I’ve got a function bar > which is compiled by
2008 Jan 09
7
An "R is slow"-article
Hi all, Reading the wikipedia page on R, I stumbled across the following: http://fluff.info/blog/arch/00000172.htm It does seem interesting that the C execution is that much slower from R than from a native C program. Could any of the more technically knowledgeable people explain why this is so? The author also have some thought-provoking opinions on R being no-good and that you should write
2002 Jun 13
3
[R] help debugging segfaults
...mes = 0; > > 1847 if (dup) { > > 1849 info.cargs = cargs; > > 1850 info.allArgs = args; > > 1851 info.nargs = nargs; > > 1852 info.functionName = buf; > > 1853 nargs = 0; > > 1854 for (pargs = args ; pargs != R_NilValue ; pargs = > > CDR(pargs)) { > > 1855 if(argConverters[nargs]) { > > 1864 PROTECT(s = > CPtrToRObj(cargs[nargs], CAR(pargs), > > which)); > > > > Program received signal SIGSEGV, Segmentation fault...
2008 Feb 15
1
[LLVMdev] LLVM2.2 x64 JIT trouble on VStudio build
Hey Evan, At the point of the instructions you suggested I step through, X86ISelLowering has this state: - this 0x00000000005fe728 {VarArgsFrameIndex=-842150451 RegSaveFrameIndex=-842150451 VarArgsGPOffset=3452816845 ...} llvm::X86TargetLowering * const + llvm::TargetLowering {TM={...} TD=0x00000000008edac0
2008 May 18
2
Pure win32-thread library?
Hi all, Here''s my initial stab at a pure Ruby win32-thread library that doesn''t work at all. I''m not sure how to pass the start address of the arguments to the callback. I thought about Marshal, but you can''t marshal a proc. BTW, the CreateThread method in windows-pr needs to be updated for this to have any hope of success. Any ideas? Thanks, Dan #
2006 Mar 30
8
iostat -xn 5 _donot_ update: how to use DTrace
on Solaris 10 5.10 Generic_118822-23 sun4v sparc SUNW,Sun-Fire-T200 I run #iostat -xn 5 to monitor the IO statistics on SF T2000 server. The system also have a heavy IO load, for some reason iostat donot refresh (no any update). It seems like iostat is calling pause() and stucked there. Also my HBA driver''s interrupt stack trace indicates there is a lot of swtch(), the overall IOPS
2005 Dec 27
0
can not setup ie and fonts problem
My operating system is fedora 4 for x86_64 and the linux kernel is 2.6.14.My wine version is 0.92.After complete installation,I try to setup ie6 sp1.But I get the following message.How can I solve it?And the fonts in winefile explore look so ugly.I show the snapshot in attachment.By the way my system locate is seted to be zh_CN. WINEDLLOVERRIDES="advpack=n" wine ie6setup.exe
2003 Apr 27
2
bug and proposed fix in print.trellis 1.7.0 (PR#2859)
This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. ---1678264062-154654637-1051422990=:2626055 Content-Type: TEXT/PLAIN; charset=US-ASCII ---1678264062-154654637-1051422990=:2626055 Content-Type: TEXT/PLAIN; charset=US-ASCII;
2016 Aug 29
10
[Bug 97537] New: nvc0 occasionally crashes in glDrawArrays in a multi-threaded app
https://bugs.freedesktop.org/show_bug.cgi?id=97537 Bug ID: 97537 Summary: nvc0 occasionally crashes in glDrawArrays in a multi-threaded app Product: Mesa Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component:
2006 Sep 05
4
Two submitted packages
## This example runs in R 2.3.1 and does not run in R 2.4.1. I am ## raising it here for two questions: one on how to debug functions ## inside a namespace, the other on how to control clipping. tmp <- data.frame(x=1:5, y=1:5, a=factor(c(1,1,1,1,1), levels=1:4)) xyplot(y ~ x, data=tmp, ylim=c(1.5,4.5), panel=function(x,y, ...) { cpv <- current.viewport()