search for: fc

...7.276572] RIP: 0033:0x7ffbe9a2f160 > [ 7.276574] Code: c3 48 8b 05 2a 2d 2c 00 f7 db 64 89 18 48 83 cb ff eb dd 0f 1f 80 00 00 00 00 83 3d 1d 8f 2c 00 00 75 10 b8 2e 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 31 c3 48 83 ec 08 e8 ee cb 00 00 48 89 04 24 > [ 7.276728] RSP: 002b:00007ffc5a2d6108 EFLAGS: 00000246 ORIG_RAX: 000000000000002e > [ 7.276735] RAX: ffffffffffffffda RBX: 00007ffc5a2da220 RCX: 00007ffbe9a2f160 > [ 7.276738] RDX: 0000000000000000 RSI: 00007ffc5a2d6150 RDI: 0000000000000003 > [ 7.276741] RBP: 00007ffc5a2d6150 R08: 0000000000000000 R09: 000000...

Dear list, I have a problem with defining a function (see below) to read my testfile (see testfile). My function only returns mydata I wish to work with attr(mydata, 'fc') as well (for labelling a plot). Principally it works if I do not insist on this function but it would be much easer if it is possible to return mydata AND attr(mydata, 'fc') by using a function. 1) testfile: Id;fc;zat;dat;hat PG;1,3;1;2;3 HU;2,5;0;2;5 JZ;1,8;1;0;4 2) my function:...

...15 > Bridge firewalling registered > can: controller area network core (rev 20170425 abi 9) > NET: Registered protocol family 29 > can: raw protocol (rev 20170425) > can: broadcast manager protocol (rev 20170425 t) > can: netlink gateway (rev 20170425) max_hops=1 > Bluetooth: RFCOMM TTY layer initialized > Bluetooth: RFCOMM socket layer initialized > Bluetooth: RFCOMM ver 1.11 > Bluetooth: BNEP (Ethernet Emulation) ver 1.3 > Bluetooth: BNEP filters: protocol multicast > Bluetooth: BNEP socket layer initialized > Bluetooth: HIDP (Human Interface Emulation)...

...15 > Bridge firewalling registered > can: controller area network core (rev 20170425 abi 9) > NET: Registered protocol family 29 > can: raw protocol (rev 20170425) > can: broadcast manager protocol (rev 20170425 t) > can: netlink gateway (rev 20170425) max_hops=1 > Bluetooth: RFCOMM TTY layer initialized > Bluetooth: RFCOMM socket layer initialized > Bluetooth: RFCOMM ver 1.11 > Bluetooth: BNEP (Ethernet Emulation) ver 1.3 > Bluetooth: BNEP filters: protocol multicast > Bluetooth: BNEP socket layer initialized > Bluetooth: HIDP (Human Interface Emulation)...

...null) flags=0x200000000004080 INFO: Object 0xffff880169e20000 @offset=0 fp=0x (null) Object ffff880169e20000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Object ffff880169e20010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ ... Object ffff880169e20fc0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ff ff ................ Object ffff880169e20fd0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Object ffff880169e20fe0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ff ff ................ Object ffff880169e20ff0: 00 00 00 00 00 00 00 00...

This fixes some nasty issues I found in nouveau that were being caused looping through connectors using racy legacy methods, along with some caused by making incorrect assumptions about the drm_connector structs in nouveau's connector list. Most of these memory corruption issues could be reproduced by using an MST hub with nouveau. Cc: Karol Herbst <karolherbst at gmail.com> Cc: stable

...gistered > > can: controller area network core (rev 20170425 abi 9) > > NET: Registered protocol family 29 > > can: raw protocol (rev 20170425) > > can: broadcast manager protocol (rev 20170425 t) > > can: netlink gateway (rev 20170425) max_hops=1 > > Bluetooth: RFCOMM TTY layer initialized > > Bluetooth: RFCOMM socket layer initialized > > Bluetooth: RFCOMM ver 1.11 > > Bluetooth: BNEP (Ethernet Emulation) ver 1.3 > > Bluetooth: BNEP filters: protocol multicast > > Bluetooth: BNEP socket layer initialized > > Bluetooth: HID...

Hello all, I am trying to debug an elusive memory corruption bug on my arm64 machine which appears to be in the nouveau driver. I got the following splat from the refcount debugging code: """ refcount_t: underflow; use-after-free. ------------[ cut here ]------------ WARNING: CPU: 0 PID: 3366 at lib/refcount.c:128 refcount_sub_and_test+0xe8/0x108 Modules linked in: fuse nouveau ttm drm_kms_helper drm ip_tables x_tables ipv6 CPU: 0 PID: 3366 Comm:...

...om_fork+0x3a/0x50 [ 201.039441] [ 201.039444] Allocated by task 79: [ 201.039449] save_stack+0x43/0xd0 [ 201.039452] kasan_kmalloc+0xc4/0xe0 [ 201.039456] kmem_cache_alloc_trace+0x10a/0x260 [ 201.039494] nv50_mstm_add_connector+0x9a/0x340 [nouveau] [ 201.039504] drm_dp_add_port+0xff5/0x1fc0 [drm_kms_helper] [ 201.039511] drm_dp_send_link_address+0x4a7/0x740 [drm_kms_helper] [ 201.039518] drm_dp_check_and_send_link_address+0x1a7/0x210 [drm_kms_helper] [ 201.039525] drm_dp_mst_link_probe_work+0x71/0xb0 [drm_kms_helper] [ 201.039529] process_one_work+0x7a0/0x14d0 [ 201.039533]...

.../lib/libR.so(Rf_eval+0x3c3)[0x7fb437877be3] /usr/lib64/R/lib/libR.so[0x7fb43787b39c] /usr/lib64/R/lib/libR.so(R_execMethod+0x241)[0x7fb43787b6d1] /usr/lib64/R/library/methods/libs/methods.so[0x7fb435259655] /usr/lib64/R/lib/libR.so[0x7fb4378c205c] /usr/lib64/R/lib/libR.so(Rf_eval+0x5dc)[0x7fb437877dfc] /usr/lib64/R/lib/libR.so[0x7fb43787802f] /usr/lib64/R/lib/libR.so(Rf_eval+0x26d)[0x7fb437877a8d] /usr/lib64/R/lib/libR.so(Rf_eval+0x64b)[0x7fb437877e6b] /usr/lib64/R/lib/libR.so[0x7fb43787802f] /usr/lib64/R/lib/libR.so(Rf_eval+0x26d)[0x7fb437877a8d] /usr/lib64/R/lib/libR.so(Rf_eval+0x64b)[0x7fb437...

...tten at Thu, 6 Jul 2017 13:58:10 -0400 >>> On 06/07/2017 5:21 AM, Serguei Sokol wrote: >>>> I propose the following patch against the current >>>> R-devel/src/main/connection.c (cf. attached file). >>>> It gives (on my linux box): >>>> > fc=file("/dev/full", "w") >>>> > write.csv("a", file=fc) >>>> Error in writeLines(paste(col.names, collapse = sep), file, sep = eol) : >>>> system call failure on writing >>>> > close(fc) >>>> >>...

I have an old (1997) Best Ferrups (model FE18KVA) that I am trying to monitor for the first time, but all the Best drivers fail to communicate with it. In ups_sync() in bestuferrups.c and bestfcom.c, the "time" command is sent and a one-line response is read. However, on my UPS, that command returns the current time and then prompts for a new time setting. I worked around that by just sending another "\r" (on an UPS that doesn't prompt for the time that will just...

...>>>>> On 06/07/2017 5:21 AM, Serguei Sokol wrote: >>>>>> I propose the following patch against the current >>>>>> R-devel/src/main/connection.c (cf. attached file). >>>>>> It gives (on my linux box): >>>>>> > fc=file("/dev/full", "w") >>>>>> > write.csv("a", file=fc) >>>>>> Error in writeLines(paste(col.names, collapse = sep), file, sep = eol) : >>>>>> system call failure on writing >>>>>> > clo...

On Mon, Apr 6, 2020 at 8:46 AM syzbot <syzbot+d3a7951ed361037407db at syzkaller.appspotmail.com> wrote: > > Hello, > > syzbot found the following crash on: > > HEAD commit: ffc1c20c Merge tag 'for-5.7/dm-changes' of git://git.kerne.. > git tree: upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=1690471fe00000 > kernel config: https://syzkaller.appspot.com/x/.config?x=d6a1e2f9a9986236 > dashboard link: https://syzkaller.appspot...

On Mon, Apr 6, 2020 at 8:46 AM syzbot <syzbot+d3a7951ed361037407db at syzkaller.appspotmail.com> wrote: > > Hello, > > syzbot found the following crash on: > > HEAD commit: ffc1c20c Merge tag 'for-5.7/dm-changes' of git://git.kerne.. > git tree: upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=1690471fe00000 > kernel config: https://syzkaller.appspot.com/x/.config?x=d6a1e2f9a9986236 > dashboard link: https://syzkaller.appspot...

...to be taken off the bug repository and continued here. By now it seems pretty clear that this is not an R bug, but a local problem on Spencer's machine, likely connected to font configurations. Or even on R-sig-Mac. > I poked around a bit on the three Macs that I can access, and found that fc-match does different things, including throwing warnings, hanging and even crashing my old MB Air... > > One possible reason is that it can apparently be installed in multiple locations, for reasons lost in the mists of time: > > Peters-iMac:BUILD-dist pd$ ls -l /opt/local/bin/fc-* &g...

...nee: nouveau at lists.freedesktop.org Reporter: ard.biesheuvel at linaro.org QA Contact: xorg-team at lists.x.org Hello all, I am trying to debug an elusive memory corruption bug on my arm64 machine which appears to be in the nouveau driver. I got the following splat from the refcount debugging code: """ refcount_t: underflow; use-after-free. ------------[ cut here ]------------ WARNING: CPU: 0 PID: 3366 at lib/refcount.c:128 refcount_sub_and_test+0xe8/0x108 Modules linked in: fuse nouveau ttm drm_kms_helper drm ip_tables x_tables ipv6 CPU: 0 PID: 3366 Comm:...

This fixes some nasty issues I found in nouveau that were being caused looping through connectors using racy legacy methods, along with some caused by making incorrect assumptions about the drm_connector structs in nouveau's connector list. Most of these memory corruption issues could be reproduced by using an MST hub with nouveau. Next version of

Seems ok on my system. Axis label size changes when cex.axis does. ## tested in the middle of another long session, so many additional packages are attached, including some personal packages not available elsewhere > sessionInfo() R version 3.5.1 (2018-07-02) Platform: x86_64-apple-darwin15.6.0 (64-bit) Running under: macOS High Sierra 10.13.6 Matrix products: default BLAS:

...quot;,"\"quoted simpleline\"" > > # write it out > write.table(data, sep=",", row.names=FALSE, file=filename) > > # reading it in a line is missing > read.csv(filename) a b 1 e\nnewline \\quoted simpleline\\ > > fc <- file(filename, open="r") > > # the problem seems to be > # readTableHead erroneously counts 3 lines as 4 > lines <- .Internal(readTableHead(fc, 4, "", TRUE)) > lines [1] "\"a\",\"b\"" "\&quot...