From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: q-tools OOPS
Date: Mon, 08 Dec 2003 23:33:54 +0000 [thread overview]
Message-ID: <marc-linux-ia64-107092647632665@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-107092374429612@msgid-missing>
>>>>> On Tue, 9 Dec 2003 09:46:18 +1100, Peter Chubb <peter@chubb.wattle.id.au> said:
Peter> Hi David,
Peter> Dunno what's going on here. I've built q-tools against libpfm3.0
Peter> and libc 2.3.2.ds1-10.0.1 from Debian using gcc 3.2.3.
Sounds fine.
Peter> When run on a vanilla 2.6.0-test11 kernel, I either get no output, or
Peter> an OOPS. stracing q-syscollect always shows a SEGV in the child
Peter> processes, but I think that may be an strace bug.
Peter> I guess that this *could* be a preemption problem; have you run
Peter> q-syscollect on a machine with CONFIG_PREEMPT on?
Nope, I definitely haven't tried CONFIG_PREEMPT. It's obviously a
kernel bug, since q-syscollect doesn't do anything nasty---it's a pure
user-level program. Can you try without CONFIG_PREEMPT?
--david
next prev parent reply other threads:[~2003-12-08 23:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-08 22:46 q-tools OOPS Peter Chubb
2003-12-08 23:28 ` Stephane Eranian
2003-12-08 23:33 ` David Mosberger [this message]
2003-12-08 23:50 ` Peter Chubb
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=marc-linux-ia64-107092647632665@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox