On Sun, Nov 15, 2009 at 12:17 PM, Patrick Scott <[email protected]> wrote:

> There really isn't any output besides the png saved to the sdcard. You
> should definitely not see a segfault though.


Oh, I had thought that webcore_test used for performance measurements, i.e.
page rendering timing. What is the TimerClient used for then? I was hoping
to get a native page load timer. I've looked at the page_cycler stuff but it
seems like it only dumps the render tree and memory usage information to
file. It does show a report.html file in the HTMLViewer, but I'm not sure
how one would save the dynamic output to file.

Was there anything in logcat after the segfault? Usually debuggerd catches
> the crash and will output the stack trace. That could at least give me an
> idea where the crash happened.
>

I/DEBUG   (   27): pid: 301, tid: 301  >>> /data/local/webcore_test <<<
I/DEBUG   (   27): signal 11 (SIGSEGV), fault addr deadbaad
I/DEBUG   (   27):  r0 00000027  r1 3fe2f250  r2 3fe2f275  r3 3fe1066d
I/DEBUG   (   27):  r4 3fe37e08  r5 3fe2f250  r6 deadbaad  r7 3fe3a9c4
I/DEBUG   (   27):  r8 00000000  r9 00000000  10 00000000  fp 00000000
I/DEBUG   (   27):  ip 00000a31  sp bee4fa98  lr 3fe1f385  pc 3fe10676  cpsr
20000030
I/DEBUG   (   27):          #00  pc 00010676  /system/lib/libc.so
I/DEBUG   (   27):          #01  pc 0000b03e  /system/lib/libc.so
I/DEBUG   (   27):          #02  pc 0001cdf8  /data/local/webcore_test
I/DEBUG   (   27):          #03  pc 0009c74e  /data/local/webcore_test
I/DEBUG   (   27):          #04  pc 0001bd90  /data/local/webcore_test
I/DEBUG   (   27):          #05  pc 0001c60c  /data/local/webcore_test
I/DEBUG   (   27):          #06  pc 0000bf86  /system/lib/libc.so
I/DEBUG   (   27):          #07  pc 700016d0  /system/bin/linker
I/DEBUG   (   27): stack:
I/DEBUG   (   27):     bee4fa58  3fe3ab7c
I/DEBUG   (   27):     bee4fa5c  3fe0edc4  /system/lib/libc.so
I/DEBUG   (   27):     bee4fa60  3fe3802c  /system/lib/libc.so
I/DEBUG   (   27):     bee4fa64  3fe37fd8  /system/lib/libc.so
I/DEBUG   (   27):     bee4fa68  00000000
I/DEBUG   (   27):     bee4fa6c  3fe13d1d  /system/lib/libc.so
I/DEBUG   (   27):     bee4fa70  00000000
I/DEBUG   (   27):     bee4fa74  1d333c93
I/DEBUG   (   27):     bee4fa78  3fe3a9c4
I/DEBUG   (   27):     bee4fa7c  3fe37e08  /system/lib/libc.so
I/DEBUG   (   27):     bee4fa80  3fe2f250  /system/lib/libc.so
I/DEBUG   (   27):     bee4fa84  00002ee0
I/DEBUG   (   27):     bee4fa88  3fe3a9c4
I/DEBUG   (   27):     bee4fa8c  3fe1066d  /system/lib/libc.so
I/DEBUG   (   27):     bee4fa90  df002777
I/DEBUG   (   27):     bee4fa94  e3a070ad
I/DEBUG   (   27): #00 bee4fa98  3fe3ab7c
I/DEBUG   (   27):     bee4fa9c  3fe0edc4  /system/lib/libc.so
I/DEBUG   (   27):     bee4faa0  3fe37e08  /system/lib/libc.so
I/DEBUG   (   27):     bee4faa4  003fefc8  [heap]
I/DEBUG   (   27):     bee4faa8  00000003
I/DEBUG   (   27):     bee4faac  fffffbdf
I/DEBUG   (   27):     bee4fab0  3fe37e08  /system/lib/libc.so
I/DEBUG   (   27):     bee4fab4  003ff1d0  [heap]
I/DEBUG   (   27):     bee4fab8  0000002a
I/DEBUG   (   27):     bee4fabc  3fe0b043  /system/lib/libc.so
I/DEBUG   (   27): #01 bee4fac0  00000006
I/DEBUG   (   27):     bee4fac4  3fe3ab00
I/DEBUG   (   27):     bee4fac8  00000004
I/DEBUG   (   27):     bee4facc  3fe3a9c4
I/DEBUG   (   27):     bee4fad0  3c14050c  /system/lib/libskia.so
I/DEBUG   (   27):     bee4fad4  3fe3aaf0
I/DEBUG   (   27):     bee4fad8  00000004
I/DEBUG   (   27):     bee4fadc  3fe3ab00
I/DEBUG   (   27):     bee4fae0  3c13eb28  /system/lib/libskia.so
I/DEBUG   (   27):     bee4fae4  003fefc8  [heap]
I/DEBUG   (   27):     bee4fae8  3c03ea5c  /system/lib/libskia.so
I/DEBUG   (   27):     bee4faec  003fefcc  [heap]
I/DEBUG   (   27):     bee4faf0  3c13eb28  /system/lib/libskia.so
I/DEBUG   (   27):     bee4faf4  0001cdfb  /data/local/webcore_test

That's the end of the output.


>

> On Fri, Nov 13, 2009 at 5:05 PM, Buakaw San <[email protected]> wrote:
>
>> Also, what kind of output do you get from the successful execution of this
>> command line tool? Could you please post a sample dump of the output?
>>
>> Thanks.
>>
>> On Mon, Nov 2, 2009 at 12:58 PM, Buakaw San <[email protected]> wrote:
>>
>>> I'm trying to use webcore_test to execute performance tests, in
>>> particular measuring the speed of page loads for numerous websites.
>>> I've built webcore_test after including external/webkit/perf to the
>>> android build. I used adb push to copy it to the system. When I run
>>> the executable using adb shell, I get the following output:
>>>
>>> # ./webcore_test d
>>> virtual void WebCore::Widget::show()
>>> void WebCore::ScriptController::updatePlatformScriptObjects()
>>> void WebCore::ScriptController::updatePlatformScriptObjects()
>>> void WebCore::ScriptController::updatePlatformScriptObjects()
>>>
>>> Not sure where this output is coming from. From looking at the code it
>>> would seem that it should prompt for a web address then load it in a
>>> webview and save the image to the sdcard.
>>>
>>> What is going on here? How do I use this command line utility
>>> properly?
>>>
>>> Thanks.
>>
>>
>>
>

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to