ALT Linux Team development discussions
 help / color / mirror / Atom feed
* [devel] system(3) blocks alarm(2) under strace(1)
@ 2004-06-23  8:39 Alexey Tourbin
  2004-06-23 13:29 ` Dmitry V. Levin
  0 siblings, 1 reply; 2+ messages in thread
From: Alexey Tourbin @ 2004-06-23  8:39 UTC (permalink / raw)
  To: devel


[-- Attachment #1.1: Type: text/plain, Size: 226 bytes --]

Столкнулся в перле, но воспроизводится без всякого перла.

$ gcc alarm.c
$ ./a.out
diff=3 seconds
$ strace -o /dev/null ./a.out
diff=3 seconds
$ strace -f -o /dev/null ./a.out
diff=6 seconds
$

В чем здесь секрет?

[-- Attachment #1.2: alarm.c --]
[-- Type: text/plain, Size: 362 bytes --]

#include <stdio.h>
#include <unistd.h>
#include <stdlib.h>
#include <signal.h>
#include <time.h>

time_t start_time, alarm_time;

void alarm_handler(int signo)
{
	alarm_time = time(NULL);
}

int main()
{
	start_time = time(NULL);
	signal(SIGALRM, alarm_handler);
	alarm(3);
	system("sleep 6");
	printf("diff=%d seconds\n", alarm_time - start_time);
	return 0;
}

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [devel] system(3) blocks alarm(2) under strace(1)
  2004-06-23  8:39 [devel] system(3) blocks alarm(2) under strace(1) Alexey Tourbin
@ 2004-06-23 13:29 ` Dmitry V. Levin
  0 siblings, 0 replies; 2+ messages in thread
From: Dmitry V. Levin @ 2004-06-23 13:29 UTC (permalink / raw)
  To: ALT Devel discussion list

[-- Attachment #1: Type: text/plain, Size: 1047 bytes --]

On Wed, Jun 23, 2004 at 12:39:37PM +0400, Alexey Tourbin wrote:
> Столкнулся в перле, но воспроизводится без всякого перла.
> 
> $ gcc alarm.c
> $ ./a.out
> diff=3 seconds
> $ strace -o /dev/null ./a.out
> diff=3 seconds
> $ strace -f -o /dev/null ./a.out
> diff=6 seconds
> $
> 
> В чем здесь секрет?

В strace(1) про -f написано:

Trace child processes as they are created by currently traced processes
as a result of the fork(2) system call.  The new process is attached
to as soon as its pid is known (through the return value of fork(2) in
the parent process). This means that such children may run uncontrolled
for a while (especially in the case of a vfork(2)), until the parent is
scheduled again to complete its (v)fork(2) call.

If the parent process decides to wait(2) for a child that is currently
being traced, it is suspended until an appropriate child process either
terminates or incurs a signal that would cause it to terminate (as
determined from the child's current signal disposition).


-- 
ldv

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2004-06-23 13:29 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-06-23  8:39 [devel] system(3) blocks alarm(2) under strace(1) Alexey Tourbin
2004-06-23 13:29 ` Dmitry V. Levin

ALT Linux Team development discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
		devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
	public-inbox-index devel

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git