Hello again,
Here comes the strace result:
...
rt_sigaction(SIGINT, {SIG_DFL}, {SIG_DFL}, 16) = 0
rt_sigaction(SIGQUIT, {SIG_DFL}, {SIG_DFL}, 16) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [RT_0], 16) = 0
fork() = 1026
waitpid(1026, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0) = 1026
rt_sigaction(SIGINT, {SIG_DFL}, NULL, 16) = 0
rt_sigaction(SIGQUIT, {SIG_DFL}, NULL, 16) = 0
rt_sigprocmask(SIG_SETMASK, [RT_0], NULL, 16) = 0
--- SIGCHLD (Child exited) @ 0 (0) ---
rt_sigaction(SIGINT, {SIG_DFL}, {SIG_DFL}, 16) = 0
rt_sigaction(SIGQUIT, {SIG_DFL}, {SIG_DFL}, 16) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [RT_0], 16) = 0
fork() = 1028
waitpid(1028, 0x7fa4955c, 0) = ? ERESTARTSYS (To be restarted)
--- SIGHUP (Hangup) @ 0 (0) ---
+++ killed by SIGHUP +++
With strace my program crashes...
strace -f doesnt work because of mipsel arch.
First fork() ist following command:
system("mv file1 /tmp/file2");
Second fork() is the system call with gzip command:
system("tar -cj -ffile3 /tmp/file2");
Any hints?
Bye
Uwe
> How did you conclude that it's not busybox/tar's fault?
> system("tar ..."); should normally return 0,
> so something is definitely is not working right.
> It may be a busybox tar problem.
> We do not have enough info yet to know, but the fact that
> tar file gets created tells that tar was successfully exec'ed.
> (it's not fork or exec failure, that is)
>
> Uwe, can you "strace -f -o LOGFILE your_program"? It will show
> what's going on.
>
> Does it ever happen when you run the very same tar command from
> command line?
> --
> vda
>
_______________________________________________
busybox mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/busybox
