From: Mark Wielaard <mark@klomp.org>
To: frysk@sourceware.org
Subject: FYI quick ftrace build fix for FC6
Date: Mon, 01 Oct 2007 09:10:00 -0000 [thread overview]
Message-ID: <1191229827.3842.29.camel@dijkstra.wildebeest.org> (raw)
Hi,
the java source parser on FC6 seems to not like one particular construct
in the new ftrace code. So this patch expands the one source line to
make it easier for the compiler to parse:
2007-10-01 Mark Wielaard <mwielaard@redhat.com>
* ObjectFile.java (ObjFBuilder.getTracePoints):
Expand ElfSymbol.Loader.loadAll() sequence.
Committed,
Mark
diff -u -r1.5 ObjectFile.java
--- frysk-core/frysk/ftrace/ObjectFile.java 29 Sep 2007 16:46:58 -0000 1.5
+++ frysk-core/frysk/ftrace/ObjectFile.java 1 Oct 2007 09:07:51 -0000
@@ -260,7 +260,9 @@
this.tracePoints = new ArrayList();
this.tracePointMap.put(this.origin, this.tracePoints);
- new ElfSymbol.Loader(ObjectFile.this.staticSymtab).loadAll(this);
+ ElfSymbol.Loader loader;
+ loader = new ElfSymbol.Loader(ObjectFile.this.staticSymtab);
+ loader.loadAll(this);
}
return this.tracePoints;
reply other threads:[~2007-10-01 9:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1191229827.3842.29.camel@dijkstra.wildebeest.org \
--to=mark@klomp.org \
--cc=frysk@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).