linux-kernel - ERESTARTNOINTR, when compiling/linking shotwell with -pg

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <loom.20110815T013533-483@post.gmane.org>
Date:	Sun, 14 Aug 2011 23:45:51 +0000 (UTC)
From:	Oliver <oliver@...st.in-berlin.de>
To:	linux-kernel@...r.kernel.org
Subject: ERESTARTNOINTR, when compiling/linking shotwell with -pg

Hello,

I added "-pg" switches to shotwell-Makefile and when running my
profiling-shotwell, when quitting it, it hangs temporarily.

"temporarily" can be between about 9 and more than 38 minutes (any other value
might also be possible... but these are some min/max numbers I experienced. In
case of 38 minutes it was "only" 38 minutes, because I killed shotwell after
that time.)

Without the "-pg" switch I did not got that problem.

Strace tells me, that the profiling timer expired.

Here some lines of strace, which I got, when the programs hangs:

  [...]
  clone(child_stack=0, flags=CLONE_PARENT_SETTID|SIGCHLD,
parent_tidptr=0x7fffdcc6ac8c) = ? ERESTARTNOINTR (To be restarted)
  --- {si_signo=SIGPROF, si_code=SI_KERNEL, si_value={int=1, ptr=0x1}}
(Profiling timer expired) ---
  rt_sigreturn(0x1b)                      = 56
  clone(child_stack=0, flags=CLONE_PARENT_SETTID|SIGCHLD,
parent_tidptr=0x7fffdcc6ac8c) = ? ERESTARTNOINTR (To be restarted)
  --- {si_signo=SIGPROF, si_code=SI_KERNEL, si_value={int=1, ptr=0x1}}
(Profiling timer expired) ---
  rt_sigreturn(0x1b)                      = 56
  [...]

Using current standard installation of Arch linux on AMD-64 dual-core (no custom
kernel).

Any idea on fixing this?

As far as I could find out, this seems to be a kernel-problem.
So it's, why I let you know it here.

Ciao,
   Oliver

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/