On Thu, Mar 6, 2014 at 8:01 PM, Philippe Ombredanne
wrote:
> On Tue, Mar 4, 2014 at 1:59 PM, Zubin Mithra wrote:
>> Hey Philippe,
>>
>>> Just curious, why would you use call_one? and arg1,arg2 v.s using lists?
>>
>> I was just wondering if information related to the call sequence might
>> be use
Decode siginfo_t more clearly for si_code SI_TIMER.
The 'pid' is actually a POSIX timer id, and the 'uid' is actually the overrun.
Also factor out the si_value dumping so it's the same for every si_code.
Signed-off-by: Elliott Hughes
diff --git a/signal.c b/signal.c
index ce8ec0a..69fea37 10064
On 04/03/14 17:41, William Manley wrote:
> + case VIDIOC_TRY_FMT:
> + case VIDIOC_S_FMT:
> + {
> + /* TODO: work out how strace deals with inout arguments
> and
> +implement */
> + return 0;
> +
> On Sun, Mar 2, 2014 at 4:26 AM, Philippe Ombredanne
> wrote:
>> On Fri, Feb 28, 2014 at 2:53 AM, enh wrote:
>>> and this fixes decoding of fstat64 and friends for an arm32 binary
>>> traced by an arm64 strace...
>>
>> Elliott:
>> Beyond this do you think that there would be enough meat to have
On Mon, Mar 3, 2014 at 10:15 PM, enh wrote:
> On Sun, Mar 2, 2014 at 3:39 AM, Philippe Ombredanne
> wrote:
>> On Tue, Feb 25, 2014 at 8:49 PM, enh wrote:
[...]
>> On the pipes side, I am a bit more puzzled as what more could be done
>>
>> pipe(2) has nothing we could decode afaik?
>>
>> Are
On Tue, Mar 4, 2014 at 1:59 PM, Zubin Mithra wrote:
> Hey Philippe,
>
>> Just curious, why would you use call_one? and arg1,arg2 v.s using lists?
>
> I was just wondering if information related to the call sequence might
> be useful. In quite a few languages, JSON data directly maps to
> dictiona
