* [Bug runtime/5213] x86_64 with 2.6.23 kernel seems to miss rt_sigaction for 32-bit code
[not found] <bug-5213-6586@http.sourceware.org/bugzilla/>
@ 2015-11-28 14:16 ` fche at redhat dot com
0 siblings, 0 replies; 3+ messages in thread
From: fche at redhat dot com @ 2015-11-28 14:16 UTC (permalink / raw)
To: systemtap
https://sourceware.org/bugzilla/show_bug.cgi?id=5213
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |fche at redhat dot com
Resolution|--- |WORKSFORME
--- Comment #3 from Frank Ch. Eigler <fche at redhat dot com> ---
current tapsets cover rt_sigaction{,32} symmetrically
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug runtime/5213] x86_64 with 2.6.23 kernel seems to miss rt_sigaction for 32-bit code
2007-10-23 18:00 [Bug runtime/5213] New: " wcohen at redhat dot com
2007-10-23 18:08 ` [Bug runtime/5213] " wcohen at redhat dot com
@ 2008-02-22 22:29 ` mhiramat at redhat dot com
1 sibling, 0 replies; 3+ messages in thread
From: mhiramat at redhat dot com @ 2008-02-22 22:29 UTC (permalink / raw)
To: systemtap
------- Additional Comments From mhiramat at redhat dot com 2008-02-22 22:28 -------
In tapset/syscalls2.stp, syscall.rt_sigaction uses _struct_sigaction_u($act) to
get the signal handler. On the other hand, syscall.rt_sigaction32 doesn't use
that. Thus, it can not get the actual handler address.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=5213
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug runtime/5213] x86_64 with 2.6.23 kernel seems to miss rt_sigaction for 32-bit code
2007-10-23 18:00 [Bug runtime/5213] New: " wcohen at redhat dot com
@ 2007-10-23 18:08 ` wcohen at redhat dot com
2008-02-22 22:29 ` mhiramat at redhat dot com
1 sibling, 0 replies; 3+ messages in thread
From: wcohen at redhat dot com @ 2007-10-23 18:08 UTC (permalink / raw)
To: systemtap
------- Additional Comments From wcohen at redhat dot com 2007-10-23 18:08 -------
Lines of interest in the test output:
rt_signal: rt_sigaction (SIGUSR1, 0x00000000ff8ef17c, 0x0000000000000000, 8) = \
0
rt_signal: rt_sigaction (SIGUSR1, 0x00000000ff8ef17c, 0x0000000000000000, 8) = \
0
rt_signal: rt_sigaction (SIGUSR1, 0x00000000ff8ef17c, 0x0000000000000000, 8) = \
0
--------- EXPECTED and NOT MATCHED ----------
rt_signal: rt_sigaction \(SIGUSR1, {SIG_IGN}, 0x[0]+, 8\) = 0
rt_signal: rt_sigaction \(SIGUSR1, {SIG_DFL}, 0x[0]+, 8\) = 0
rt_signal: rt_sigaction \(SIGUSR1, {[x0-9a-fA-F]+, [^,]+, [x0-9a-fA-F]+, \[SIGA\
LRM\]}, 0x[0]+, 8\) = 0
FAIL: 32-bit rt_signal
--
http://sourceware.org/bugzilla/show_bug.cgi?id=5213
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-11-28 14:16 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-5213-6586@http.sourceware.org/bugzilla/>
2015-11-28 14:16 ` [Bug runtime/5213] x86_64 with 2.6.23 kernel seems to miss rt_sigaction for 32-bit code fche at redhat dot com
2007-10-23 18:00 [Bug runtime/5213] New: " wcohen at redhat dot com
2007-10-23 18:08 ` [Bug runtime/5213] " wcohen at redhat dot com
2008-02-22 22:29 ` mhiramat at redhat dot com
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).