From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: Joel Soete <jsoe0708@tiscali.be>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] glibc 2.3.2 patches updated, still no working sysdep-cancel
Date: Wed, 26 Mar 2003 10:07:30 -0500 [thread overview]
Message-ID: <20030326150729.GC2370@systemhalted> (raw)
In-Reply-To: <3E817DB0000002C4@ocpmta1.freegates.net>
> I had to kill a 'tst-cancel-stat' because it was eating 99% of cpu usage.
> As it was evidently looping, strace -p 31611 shows me hundred of thousand
> messages: kill(31610, SIGRT_1) =-1 (no such process)
Yes, I've noticed this, and I'm not sure why it's doing that. It's the
only test that fails this way. The rest just SIGSEGV, which again means
I need to keep debugging the syscall/errno code.
I'll post an update after running some tests on my current patches.
Thanks for trying that out Joel. What hardware are you testing this on?
c.
next prev parent reply other threads:[~2003-03-26 15:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-26 7:55 [parisc-linux] glibc 2.3.2 patches updated, still no working sysdep-cancel Berthold Gunreben
2003-03-26 11:57 ` Joel Soete
2003-03-26 14:09 ` Carlos O'Donell
2003-03-26 14:21 ` Joel Soete
2003-03-26 14:17 ` Joel Soete
2003-03-26 15:07 ` Carlos O'Donell [this message]
2003-03-26 18:12 ` Joel Soete
-- strict thread matches above, loose matches on Subject: below --
2003-03-26 7:14 Berthold Gunreben
2003-03-25 17:17 [parisc-linux] Glibc 2.3.2 failures and possible fixes? Carlos O'Donell
2003-03-25 18:01 ` Joel Soete
2003-03-25 23:40 ` [parisc-linux] glibc 2.3.2 patches updated, still no working sysdep-cancel Carlos O'Donell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030326150729.GC2370@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=jsoe0708@tiscali.be \
--cc=parisc-linux@lists.parisc-linux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.