Home | History | Annotate | Download | only in coregrind

Lines Matching refs:siginfo

1369 void push_signal_frame ( ThreadId tid, const vki_siginfo_t *siginfo,
1374 Int sigNo = siginfo->si_signo;
1417 VG_(sigframe_create) (tid, esp_top_of_frame, siginfo, uc,
2100 least a non-siginfo signal gets deliviered.
2369 /* On Linux, first we have to do a sanity check of the siginfo. */
2371 /* There's a per-user limit of pending siginfo signals. If
2373 pending signals with siginfo, then new signals are
2374 delivered without siginfo. This condition can be caused
2376 as Valgrind, if it has a large number of pending siginfo
2379 Since we depend on siginfo to work out why we were sent a
2382 VG_(umsg)("Signal %d (%s) appears to have lost its siginfo; "
2386 " siginfo structures. For more information, see:\n"
2389 " pending signals, and this causes the siginfo data for other signals to\n"
2391 " absolutely needs siginfo for SIGSEGV. A workaround is to track down the\n"