Hi Avery,
Nice catch. Looks like the job_trove_bstream_read_list call sets
parameters and returns, so the result.bytes field is actually out of
scope later (as part of the one element array passed in). It doesn't
always segfault because the value remains unchanged, even though its
unal
Hi Avery,
Yup.. Your fix is correct, but let's wait for Sam's comments..
Why exactly is result.bytes different from s_op->u.small_io.result_bytes?
I wonder how this did not get triggered in the normal scenarios (perhaps
it needed a sparse data file or something?)
Thanks,
Murali
On Mon, 22 May 200
I kept getting segmentation faults with the read case in the small I/O
state machine. I think there's a problem with the parameter passed in
to job_trove_bstream_read_list() around line 194 of small-io.sm.
instead of:
&result.bytes,
I think it should be:
&s_op->u.small_io
