On Sun, 27 Aug 2006 14:39:45 +0300
Eugen Minciu [EMAIL PROTECTED] wrote:
Sorry, I ran the debug again. It isn't corrupted. There was a \000 at the end
of the string like there should have been, it was just gdb printing more data
beyond that \000
The command that get executed is:
On Sun, 27 Aug 2006 14:50:24 +0300
Eugen Minciu [EMAIL PROTECTED] wrote:
I found out what was causing the problem. Just like it says in the code.
/* FIXME: need to parse command and NOT go thru /bin/sh */
/* why? some /bin/sh's wont pass on this SIGUSR1 thing... */
apparenty dash
Fixed it.
Here's a patch that runs /bin/bash first.
If that doesn't work execl should return so the next line should run after that
( execl(/bin/sh, ...)
I also found the same issue when entrace starts the session. The same fix
finally got everything working corectly.
BTW, I'm new to this
Eugen Minciu wrote:
Fixed it.
Here's a patch that runs /bin/bash first.
If that doesn't work execl should return so the next line should run after
that ( execl(/bin/sh, ...)
I also found the same issue when entrace starts the session. The same fix
finally got everything working
On 8/27/06, Eugen Minciu [EMAIL PROTECTED] wrote:
Fixed it.
Here's a patch that runs /bin/bash first.
If that doesn't work execl should return so the next line should run after
that ( execl(/bin/sh, ...)
I also found the same issue when entrace starts the session. The same fix
finally
On Sun, 27 Aug 2006 19:13:25 +0300 Eugen Minciu [EMAIL PROTECTED] babbled:
Fixed it.
Here's a patch that runs /bin/bash first.
If that doesn't work execl should return so the next line should run after
that ( execl(/bin/sh, ...)
I also found the same issue when entrace starts the
