On 2013-12-17 02:52, Chris Johns wrote:
On 17/12/2013 12:29 am, Sebastian Huber wrote:
Pass also zero-size buffers to the write handler since they may have
side-effects for non-regular files, e.g. sending of an empty message.
I agree regular files should follow the standard with others being u
On 2013-12-16 20:17, Jennifer Averett wrote:
Attached is an patch for a set of tests that checks the fixed size
functionali8ty in cpuset.h
Any comments, questions, suggestions?
Do we really need five different test programs. Can't we use one test program
with five test functions?
--
Sebas
On 2013-12-16 21:17, Joel Sherrill wrote:
On 12/16/2013 1:58 AM, Sebastian Huber wrote:
>On 2013-12-14 19:32, Joel Sherrill wrote:
>>Hi
>>
>>The failures on sis on the head indicate a few that need
>>some attention.
>>
>>WARNING - heapwalk did not appear to complete execution
>>
>> cre
On 2013-12-17 01:58, Joel Sherrill wrote:
Hi
mips/jmr3904 faults on this but I confirmed psim has the
same failure. watchpoints do not seem to be working on
either
countTaskAsync: elapsed time (second): 1
countTaskAsync: elapsed time (second): 2
countTaskAsync: elapsed time (second): 3
coun
On 17/12/2013 12:29 am, Sebastian Huber wrote:
Pass also zero-size buffers to the write handler since they may have
side-effects for non-regular files, e.g. sending of an empty message.
I agree regular files should follow the standard with others being
unspecified. I do not think this patch do
Hi
mips/jmr3904 faults on this but I confirmed psim has the
same failure. watchpoints do not seem to be working on
either
countTaskAsync: elapsed time (second): 1
countTaskAsync: elapsed time (second): 2
countTaskAsync: elapsed time (second): 3
countTaskAsync: elapsed time (second): 4
mips-c
On 12/16/2013 1:58 AM, Sebastian Huber wrote:
> On 2013-12-14 19:32, Joel Sherrill wrote:
>> Hi
>>
>> The failures on sis on the head indicate a few that need
>> some attention.
>>
>> WARNING - heapwalk did not appear to complete execution
>>
>> create a loop in the free list
>> ../../../.
On 2013-12-16 14:29, Sebastian Huber wrote:
@@ -325,11 +330,11 @@ int doErrorTest(void)
/* writev -- iov_len total overflows */
vec[0].iov_base = vec;
- vec[0].iov_len = SIZE_MAX;
+ vec[0].iov_len = INT_MAX;
vec[1].iov_base = vec;
- vec[1].iov_len = SIZE_MAX;
+ vec[1].iov_len =
The readv() and writev() support was implemented in terms of single
calls to the read and write handlers. This imposes a problem on device
files which use an IO vector as single request entity. For example a
low-level network device (e.g. BPF(4)) may use an IO vector to create
one frame from mult
Pass also zero-size buffers to the write handler since they may have
side-effects for non-regular files, e.g. sending of an empty message.
---
cpukit/libcsupport/include/rtems/libio_.h | 56
cpukit/libcsupport/src/readv.c| 88 +-
cpukit/libc
---
c/src/lib/libbsp/shared/umon/tfsDriver.c|2 ++
cpukit/libblock/src/blkdev-imfs.c |2 ++
cpukit/libcsupport/src/__usrenv.c |2 ++
cpukit/libfs/src/defaults/default_handlers.c|2 ++
cpukit/libfs/src/devfs/devfs_init.c |2 ++
11 matches
Mail list logo