From d4f98de575b93ce541a82c6102b3d05e1ef900bb Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Wed, 6 Oct 2010 20:38:11 +0200 Subject: open_issues/sa_siginfo_sa_sigaction: New. --- open_issues/sa_siginfo_sa_sigaction.mdwn | 45 ++++++++++++++++++++++++++++++++ 1 file changed, 45 insertions(+) create mode 100644 open_issues/sa_siginfo_sa_sigaction.mdwn (limited to 'open_issues') diff --git a/open_issues/sa_siginfo_sa_sigaction.mdwn b/open_issues/sa_siginfo_sa_sigaction.mdwn new file mode 100644 index 00000000..04207c61 --- /dev/null +++ b/open_issues/sa_siginfo_sa_sigaction.mdwn @@ -0,0 +1,45 @@ +[[!meta copyright="Copyright © 2010 Free Software Foundation, Inc."]] + +[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable +id="license" text="Permission is granted to copy, distribute and/or modify this +document under the terms of the GNU Free Documentation License, Version 1.2 or +any later version published by the Free Software Foundation; with no Invariant +Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license +is included in the section entitled [[GNU Free Documentation +License|/fdl]]."]]"""]] + +[[!meta title="SA_SIGINFO, SA_SIGACTION"]] + +[[!tag open_issue_glibc]] + +IRC, #hurd, August / September 2010: + + Hy, I came across SA_SIGINFO in cherokee, I have the void sighandler(int num) prototype but how do I add the sa_handler field? + if SA_SIGACTION is not defined, then you use sa_handler instead of sa_sigaction, and not add SA_SIGINFO in the sa_flags + SA_SIGINFO is not defined + s/SA_SIGACTION/SA_SIGINFO/ above, yes + K + I am not sure if I fully understand this, there is the line "act.sa_flags = SA_SIGINFO" and how do I have to change that >_> + can you paste the source in a pastebin? + k + http://archhurd.pastebin.com/N8BCnG6g at line 790 + something along the lines of http://www.archhurd.pastebin.com/tdpcFD5G + note that in the handler the siginfo_t parameter is used, which cannot be done if SA_SIGINFO is not defined + (that code still won't compile, yet) + btw: is there a reason why SA_SIGINFO is not implemented? + the guildlines only say "It's not implemented" + 09:43 < azeem> signal stuff is tricky :-/ + basically it was pending on a complete rewrite by Roland, which never occured + I have an almost complete implementation, just not finished yet + (only the siginfo part) + nobody really groked that code for years until youpi showed up, but he added partial support AFAIK, not having much time on his hand + ah, he's here + :) + oh, should I just wait ? + no + k + there are OSes which don't have SA_SIGINFO + just cope with them: use sa_handler instead of sa_sigaction, and don't set SA_SIGINFO + (i.e. replace with 0 in your example) + ok + when SA_SIGINFO becomes available, it'll just be used -- cgit v1.2.3