Compiling fails for Webkit instrumentation flag WEBCORE_INSTRUMENTATION

by vrukesh » Mon, 12 Apr 2010 15:22:06 GMT

Sponsored Links
 Hi All,

In Eclair 2.1, we have enabled the flag WEBCORE_INSTRUMENTATION for
instrumenting Webkit for performance evaluation.

But, we get following compiling errors:

libwebcore.a(Parser.o): In function
`JSC::Parser::parse(JSC::JSGlobalData*, int*, JSC::UString*)':

47: undefined reference to

76: undefined reference to
`android::TimeCounter::record(android::TimeCounter::Type, char
collect2: ld returned 1 exit status

Any suggestions for solving this ?

Thanks and Regards,
Vrukesh V. Panse


Other Threads

1. Android search dialog - SingleTop

I'm adding search to my app following the instructions found here:

When I make my main activity searchable, then I can search it. But, I
found the multiple search screens after multiple searches to be
annoying since I have to press back through each one. The instructions
also addressed this by suggesting I create a separate search activity
with android:launchMode="singleTop". According to the instructions, if
I add the following Meta tag to my Application in the manifest, then I
can get the searchable activity from any screen.
<meta-data android:name=""
                 android:value=".MySearchableActivity" />
However, when I try this, the searchable activity does not start when
I press the search button. If I make my searchable activity the main
activity, it works. What am I missing?

Here's my searchable activity in the manifest:
    <activity android:name="Search" >
            <action android:name="android.intent.action.SEARCH" />
        <meta-data android:name=""


2. New app listing order in Market app search

Before today, when entering a search term into the Market app, the
results at the top of the search would all be exact matches of that
search term against the app name. For example, type "translate" and
the user will see all the apps called "translate" before the "Google
Translate" result (which is by far the most downloaded translate app).

Now, this no longer happens. If you type "translate" the first result
is "Google Translate" (and no preference is given to exact matches).

Anyone else notice this?

Note: posted on this forum partly because hardly anyone reads Android
Discuss, and partly because developers need to know how their apps are
being prioritized in app search results).


3. Separate Thread to read system time

4. Using google map api on phones without the map library?

5. Developer with 26 apps gone from the market

6. Simple Context Menus

7. Needs confirmation on screen orientation on Android 2.1