Hi Jiri,
On Wed, 16 Apr 2014 15:34:32 +0200, Jiri Olsa wrote:
> On Wed, Apr 16, 2014 at 09:30:43AM +0900, Namhyung Kim wrote:
> I think that after creating the workload, all error paths
> need to release(wait) the child if there's any
Right. I'll resend v2.
Thanks,
Namhyung
--
To unsubscribe fr
On Wed, Apr 16, 2014 at 09:30:43AM +0900, Namhyung Kim wrote:
SNIP
>
> @@ -356,6 +331,7 @@ static void workload_exec_failed_signal(int signo,
> siginfo_t *info,
> static int __cmd_record(struct record *rec, int argc, const char **argv)
> {
> int err;
> + int status = 0;
> uns
Currently perf record doesn't propagate the exit status of a workload
given by the command line. But sometimes it'd useful if it's
propagated so that a monitoring script can handle errors
appropriately.
To do that, it got rid of exit handlers and run/call them directly in
the __cmd_record(). I d
3 matches
Mail list logo