You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
popen internally calls execl("/bin/sh", "sh", "-c", command, (char *)0);
which calls __execve (path, (char *const *) argv, __environ);, for some reason the internal 'sh -c' process is missing its data as can be seen from the trace_pipe log below, it appears empty:
This happens only form within popen, when I tested execl("/bin/sh", "sh", "-c", command, (char *)0); explicitly the data was traced correctly.
What could be the cause for this issue?
The text was updated successfully, but these errors were encountered:
I conducted the following test:
popen internally calls
execl("/bin/sh", "sh", "-c", command, (char *)0);
which calls
__execve (path, (char *const *) argv, __environ);
, for some reason the internal 'sh -c' process is missing its data as can be seen from the trace_pipe log below, it appears empty:This happens only form within popen, when I tested
execl("/bin/sh", "sh", "-c", command, (char *)0);
explicitly the data was traced correctly.What could be the cause for this issue?
The text was updated successfully, but these errors were encountered: