search for: bug2

arrows() seems to hang when either x or y scale of the plot is logarithmic and the arrows requested go beyond the plot (by more than a certain amount). I didn't go into C code to find it, but here's a function that exercises the bug a bit ... arrow.bug2 <- function(y0=1,y1=10,log="y") { plot(c(0.1,1),c(1,10),log=log) arrows(x0=0.5, y0=y0, x1=0.5, y1=y1, length=0.05,angle=90) } arrow.bug2() ## OK arrow.bug2(log="x") ## OK arrow.bug2(y0=0.01) ##hangs arrow.bug2(y1=11) ## OK arrow.bug2...

...in Sweave. It only occurs in the following situation: 1. define a variable in one chunk 2. use it within a subsequent figure-generating chunk 3. delete it at the end of that same chunk Then the Sweave driver chokes, not finding the variable name when generating the figure Example: % document bug2.Rnw \documentclass{article} \usepackage{Sweave} \begin{document} \SweaveOpts{eps=false} <<>>= sel <- 1:5 @ <<fig=T>>= plot(trees[sel,]) rm(sel) @ \end{document} Try to sweave: > Sweave("bug2.Rnw") Writing to file bug2.tex Processing code chunks ... 1 : ech...

...OK Running ?arith.R? Comparing ?arith.Rout? to ?arith.Rout.save? ... OK Running ?bar-gmp.R? Comparing ?bar-gmp.Rout? to ?bar-gmp.Rout.save? ... OK Running ?bar.R? Comparing ?bar.Rout? to ?bar.Rout.save? ... OK Running ?bug.R? Comparing ?bug.Rout? to ?bug.Rout.save? ... OK Running ?bug2.R? Comparing ?bug2.Rout? to ?bug2.Rout.save? ... OK Running ?chull.R? Comparing ?chull.Rout? to ?chull.Rout.save? ... OK Running ?chull2.R? Comparing ?chull2.Rout? to ?chull2.Rout.save? ... OK Running ?convert.R? Comparing ?convert.Rout? to ?convert.Rout.save? ... OK Running ?fred.R...

Hello, Is this a bug in clang, or a bug in my thinking? /Joe Armstrong /* When I compile the following program I get different answers in clang and gcc. $ gcc bug2.c $ ./a.out j = 40 $ clang bug2.c $ ./a.out j = 41 I think the correct answer is 41. If my understanding of C is correct (which, or course, it might not be) the incremented value of i++ is first made available at the next sequence point, which is after the ';' at the end...

Mark and Joel, I found two serious bugs about xattr and inline-data. the first bug: in ocfs2_mknod(), we check and found the ACL or security xattr entry could be set into inode in ocfs2_calc_xattr_init(), then don't reserve block for them. But in ocfs2_mknod_locked(), if we found ocfs2 support inline-data, then set id_count with the max_inline_data. After that, we set acl/security xattr

...ar * format, ...); Nitpick: you shouldn't do that. Now you have a potential mismatch between whet you compile and what you link to. > > int main() > { > int i, j; > i = 10; > j = i++ + 20 + i; > printf("j = %d\n",j); > return(0); > } > >  $ gcc bug2.c >  $ ./a.out >  j = 40 >  $ clang bug2.c >  $ ./a.out >  j = 41 > >  I think the correct answer is 41. If my understanding of C is correct >  (which, or course, it might not be) the incremented value of i++ is >  first made available at the next sequence point, which is...

...ow you have a potential mismatch > between whet you compile and what you link to. > >> >> int main() >> { >>  int i, j; >>  i = 10; >>  j = i++ + 20 + i; >>  printf("j = %d\n",j); >>  return(0); >> } > >> >>  $ gcc bug2.c >>  $ ./a.out >>  j = 40 >>  $ clang bug2.c >>  $ ./a.out >>  j = 41 >> >>  I think the correct answer is 41. If my understanding of C is correct >>  (which, or course, it might not be) the incremented value of i++ is >>  first made available...

On Apr 26, 2011, at 2:07 AM, Joe Armstrong wrote: > Compiles (via clang) to: > > ; ModuleID = 'test101.c' > target datalayout = > "e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:32:64-f32:32:32-f64:32:64-v64:64:64-v128:128:128-a0:0:64-f80:32:32-n8:16:32" > target triple = "i386-pc-linux-gnu" > > define i32 @main() nounwind { > %1 =

...nd) then both smbd and winbind wont start due to extra added parts in the systemd files and these are copied to /etc/systemd/system This is a debian policy confict and this should not happen. The correct and working files exact at /lib/systemd/system So after getting passed bug1 i did hit bug2. :-( you can get easy past it by removing the files in /etc/systemd/system smbd/winbind/samba/nmbd service files run : systemctl daemon-reload run : apt-get -f install then the install continues. You only see this with a new install, because these are set to "standalone server&quot...

...to be another bug above this for the MAXLINESIZE test too: if (*p =3D=3D '\n' || p =3D=3D end - 1) { nc =3D p - p0; if (*p !=3D '\n') nc++; if (nc <=3D MAXLINESIZE) { strncpy((char *)SourceLine, (char *)p0, nc); bug2 --> SourceLine[nc] =3D '\0'; SET_STRING_ELT(source, lines++, mkChar2((char *)SourceLine)); } else { /* over-long line */ char *LongLine =3D (char *) malloc(nc+1); if(!LongLine) error(_("unable...

Hi, This patch set fixes two bugs of splice_write in the virtio-console driver. [BUG1] Although pipe->nrbufs is empty, the driver tries to do splice_write. => This induces oops in sg_init_table(). [BUG2] No lock for competition of splice_write. => This induces oops in splice_from_pipe_feed() by bug of any user application. These reports are written in each patch. Changes in V2: - Fix a locking problem for error Changes in V3: - Add Reviewed-by lines and stable@ line in sign-...

Hi, This patch set fixes two bugs of splice_write in the virtio-console driver. [BUG1] Although pipe->nrbufs is empty, the driver tries to do splice_write. => This induces oops in sg_init_table(). [BUG2] No lock for competition of splice_write. => This induces oops in splice_from_pipe_feed() by bug of any user application. These reports are written in each patch. Changes in V2: - Fix a locking problem for error Changes in V3: - Add Reviewed-by lines and stable@ line in sign-...

I assumed that C floats are 32 bits and doubles 64 bits ... but This code int main(){ float f; double f1; f = 3.145; f1 = 3.145; return(0); } Compiles (via clang) to: ; ModuleID = 'test101.c' target datalayout = "e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:32:64-f32:32:32-f64:32:64-v64:64:64-v128:128:128-a0:0:64-f80:32:32-n8:16:32" target triple =

...ntation with the low order 28 bits zeroed. Why 28 bits? - 32 bits might be understandable but not 28. If I manually edit the hex constant to the exact 64 bit representation then I get an error. for example store float 0x400928F5C28F5C29, float* %f <= best possible representation llvm-as: bug2.s:11:15: error: floating point constant invalid for type so the "as if they were doubles" bit seems wrong - try clearing 24 bits store float 0x400928F5C2000000, float* %f <= low order 24 bits cleared llvm-as: bug2.s:12:18: error: floating point constant invalid for type clea...

Hi, This patch set fixes two bugs of splice_write in the virtio-console driver. [BUG1] Although pipe->nrbufs is empty, the driver tries to do splice_write. => This induces oops in sg_init_table(). [BUG2] No lock for competition of splice_write. => This induces oops in splice_from_pipe_feed() by bug of any user application. These reports are written in each patch. Changes in V2: - Fix a locking problem for error Thanks! --- Yoshihiro YUNOMAE (2): [BUGFIX] virtio/conso...

Hi, This patch set fixes two bugs of splice_write in the virtio-console driver. [BUG1] Although pipe->nrbufs is empty, the driver tries to do splice_write. => This induces oops in sg_init_table(). [BUG2] No lock for competition of splice_write. => This induces oops in splice_from_pipe_feed() by bug of any user application. These reports are written in each patch. Changes in V2: - Fix a locking problem for error Thanks! --- Yoshihiro YUNOMAE (2): [BUGFIX] virtio/conso...

While using Blindtransfer #Extension everything works fine. But how do i activate announced transfer with an Grandstream GPX2000 ? Greets Markus

...Jul 2013 [18:19:51], Yoshihiro YUNOMAE wrote: > Hi, > > This patch set fixes two bugs of splice_write in the virtio-console driver. > > [BUG1] Although pipe->nrbufs is empty, the driver tries to do splice_write. > => This induces oops in sg_init_table(). > > [BUG2] No lock for competition of splice_write. > => This induces oops in splice_from_pipe_feed() by bug of any user > application. > > These reports are written in each patch. > > Changes in V2: > - Fix a locking problem for error > > Thanks! Reviewed-b...

...Jul 2013 [13:00:43], Yoshihiro YUNOMAE wrote: > Hi, > > This patch set fixes two bugs of splice_write in the virtio-console driver. > > [BUG1] Although pipe->nrbufs is empty, the driver tries to do splice_write. > => This induces oops in sg_init_table(). > > [BUG2] No lock for competition of splice_write. > => This induces oops in splice_from_pipe_feed() by bug of any user > application. > > These reports are written in each patch. > > Changes in V2: > - Fix a locking problem for error > > Changes in V3: >...

While trying to fix swig & R2.7 I actually discovered that there is a bug in R 2.7 causing a crash (so R & swig might actually work): the bug is in ./src/main/gram.c line 3038: } else { /* over-long line */ fixthis --> char *LongLine = (char *) malloc(nc); if(!LongLine) error(_("unable to allocate space for source line %d"),