From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug lket/4420] systemtap.samples/lket.exp test crashing RHEL4U4 machine
Date: Sat, 28 Apr 2007 11:58:00 -0000 [thread overview]
Message-ID: <20070428115818.23680.qmail@sourceware.org> (raw)
In-Reply-To: <20070424200707.4420.wcohen@redhat.com>
------- Additional Comments From fche at redhat dot com 2007-04-28 12:58 -------
(In reply to comment #3)
> When running the test with -DASCII_TRACE it does not seem to crash the machine.
That is valuable information, and seems to point the figure toward the
runtime, no?
> Looking through the code the following idom is seen in much of the code:
> [...]
> When -DASCII_TRACE is used on the command line, the update_record() becomes an
> empty function and the order of the probes at a point becomes unimportant. It
> seems like it would make sense to merge those probes together to make sure that
> the operations are performed in the correct order.
I don't understand why you believe there is any problem here.
What incorrect order is possible?
--
http://sourceware.org/bugzilla/show_bug.cgi?id=4420
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2007-04-28 11:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-24 19:07 [Bug kprobes/4420] New: " wcohen at redhat dot com
2007-04-24 19:51 ` [Bug kprobes/4420] " dsmith at redhat dot com
2007-04-24 20:04 ` wcohen at redhat dot com
2007-04-27 20:40 ` [Bug lket/4420] " wcohen at redhat dot com
2007-04-28 11:58 ` fche at redhat dot com [this message]
2007-04-30 18:36 ` wcohen at redhat dot com
2007-04-30 20:51 ` wcohen at redhat dot com
2007-05-25 19:43 ` wcohen at redhat dot com
2007-05-25 19:45 ` wcohen at redhat dot com
2007-06-06 20:27 ` hunt at redhat dot com
2007-07-05 10:53 ` prasanna at in dot ibm dot com
2007-07-25 14:13 ` prasanna at in dot ibm dot com
2007-07-25 18:44 ` joshua dot i dot stone at intel dot com
2007-08-28 15:26 ` fche at redhat dot com
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=20070428115818.23680.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).