Bug 3115 - ftrace hangs if exec fails
Summary: ftrace hangs if exec fails
Status: NEW
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
Depends on:
Blocks: 2245
  Show dependency treegraph
Reported: 2006-08-23 20:42 UTC by Tom Tromey
Modified: 2008-03-30 16:13 UTC (History)
1 user (show)

See Also:
Last reconfirmed:


Note You need to log in before you can comment on or make changes to this bug.
Description Tom Tromey 2006-08-23 20:42:14 UTC
If I run ftrace and ask it to trace a nonexistent program, it prints:

execvp: No such file or directory

... and then hangs.

I would expect a sensible error message (prefaced with "ftrace: ")
and no hang.
Comment 1 Tom Tromey 2008-03-30 16:05:35 UTC
I'm pretty sure this one is fixed:

opsy. ftrace -- /bin/zardoz
Error: open: No such file or directory (file /bin/zardoz)

(Though note the not-so-great error message... instead of "Error"
I think it should probably say "ftrace")
Comment 2 Tom Tromey 2008-03-30 16:13:18 UTC
I spoke too soon.  This hang does still happen in some cases.
For me, "ftrace -- ls" hangs, but "ftrace -- zardoz" does not.
I get different errors in each case:

opsy. ftrace -- zardoz
Error: open: No such file or directory (file
opsy. ftrace -- ls
execvp: No such file or directory

Note that the error in the first case is pretty bogus.
The quagmire stuff is my working directory.
Probably the error should just say something about
"zardoz not found in path".