I'm not sure if this is a glibc issue, or a kernel issue, or a documentation issue.. It seems that raise is implemented as tkill, as evidenced by the fact that for sigaction handlers, si_code is set to SI_TKILL for raise()ed signals, when the manpages for sigaction indicate that raise should cause si_code to be set to SI_USER instead.
I would think that SI_USER is the more standards correct flag to set for raise.. But who should fix this? I don't remember this being an issue on my debian system. Is this Fedora specific?
glibc is responsible for the POSIX interfaces such as sigaction. File a bugzilla report for glibc. If such turn out to be kernel issues, we reclassify them appropriately.
On Tue, 6 Jan 2004, Roland McGrath wrote:
glibc is responsible for the POSIX interfaces such as sigaction. File a bugzilla report for glibc. If such turn out to be kernel issues, we reclassify them appropriately.
Good point. But where does one find this ability to report such a thing? I have been looking at fedora.redhat.com and could not find any reference as to where to report bugs.
Hugo.
On Wed, Jan 07, 2004 at 11:38:24AM +0100, Hugo van der Kooij wrote:
On Tue, 6 Jan 2004, Roland McGrath wrote:
glibc is responsible for the POSIX interfaces such as sigaction. File a bugzilla report for glibc. If such turn out to be kernel issues, we reclassify them appropriately.
Good point. But where does one find this ability to report such a thing? I have been looking at fedora.redhat.com and could not find any reference as to where to report bugs.
Hmm, http://fedora.redhat.com/participate/ has a url to bugzilla http://bugzilla.redhat.com/bugzilla/ but it doesn't seem to be a link.
Paul
On Wed, Jan 07, 2004 at 10:45:11AM +0000, Paul Nasrat wrote:
Hmm, http://fedora.redhat.com/participate/ has a url to bugzilla http://bugzilla.redhat.com/bugzilla/ but it doesn't seem to be a link.
Oops, the mistakes one makes when one converts text to HTML. I can't believe I missed that, my apologies. It will be fixed in the next push of the web site.
michaelkjohnson
"He that composes himself is wiser than he that composes a book." Linux Application Development -- Ben Franklin http://people.redhat.com/johnsonm/lad/
On Wed, 7 Jan 2004 11:38:24 +0100 (CET), Hugo van der Kooij wrote:
On Tue, 6 Jan 2004, Roland McGrath wrote:
glibc is responsible for the POSIX interfaces such as sigaction. File a bugzilla report for glibc. If such turn out to be kernel issues, we reclassify them appropriately.
Good point. But where does one find this ability to report such a thing? I have been looking at fedora.redhat.com and could not find any reference as to where to report bugs.
Huh? It's there directly on the front page already:
Fedora Core 1 Available
[...] and participate by either submitting bugs or submitting fixes. All bugs, requests for enhancements, and fixes should be submitted via Bugzilla [bugzilla.redhat.com].
[...]
If that (and the "Participate" menu) is not obvious enough case it becomes increasingly popular for people to just submit their reports at bugzilla.fedora.us instead, picking a completely unrelated component, something must be done about the Fedora Project pages. However I don't know what would help. Integrating an official Fedora FAQ could help.
--
On Wed, 7 Jan 2004, Michael Schwendt wrote:
On Wed, 7 Jan 2004 11:38:24 +0100 (CET), Hugo van der Kooij wrote:
On Tue, 6 Jan 2004, Roland McGrath wrote:
glibc is responsible for the POSIX interfaces such as sigaction. File a bugzilla report for glibc. If such turn out to be kernel issues, we reclassify them appropriately.
Good point. But where does one find this ability to report such a thing? I have been looking at fedora.redhat.com and could not find any reference as to where to report bugs.
Huh? It's there directly on the front page already:
Fedora Core 1 Available
[...] and participate by either submitting bugs or submitting fixes. All bugs, requests for enhancements, and fixes should be submitted via Bugzilla [bugzilla.redhat.com].
Oddly enough I can not recall the last time I saw a website that wanted to point you to other place but completely misunderstood how usefull a proper <a href> tag is.
Which is clearly missing op the participation page.
Hugo.