Re: [lttng-dev] Function Tracing Fails
please give your suggestions on previous mail.
Thanks,
Paramesh
On Tue, Aug 7, 2018 at 2:20 PM, paramesh p wrote:
> Sorry for the delayed response,
>
> @Mathieu,
> I have attached the build log. The Project I am working is Yocto
> Project based build system. My App uses the shared object "libhw.so". So,
> it built first. As I said before,below are the flag I added
>
> AM_CFLAGS += -g -O0 -finstrument-functions
> AM_CXXFLAGS += -g -O0 -finstrument-functions
>
>
> From the log I found that "-finstrument-functions" flag included in
> compiling all the source files, ' libhw.la' file and 'my_test_app'
> binary, but not included for compiling 'libhw.so'. I am not sure why? My
> question is, as you see my shared object and binary includes following so's
> "libtinyalsa.so libexpat.so libbinder.so libutils.so libhwwrapper.so
> libhardware.so libcutils.so liblog.so". Are all these need to be compiled
> with finstrument flag. In that case, it will increase my workload, since
> some of them are custom build and some from the libs and each of them might
> have their own dependents.
>
>
> @gen,
> objdump doesn't support arm architecture. So, I used
> "arm-linux-gnueabi-objdump" tool. I could see cyg information to all my
> object files but I could not see for "libhw.so" and "my_test_app" files.
> cyg information of one of my source file,
>
> $ arm-linux-gnueabi-objdump -d libhw_la-hw_api.o | grep cyg
>
> 20: ebfebl 0 <__cyg_profile_func_enter>
>
> 30: eafeb 0 <__cyg_profile_func_exit>
>
> 64: ebfebl 0 <__cyg_profile_func_enter>
>
> a4: ebfebl 0 <__cyg_profile_func_exit>
>
> .
>
> .
>
> 2548: ebfebl 0 <__cyg_profile_func_exit>
>
> 258c: ebfebl 0 <__cyg_profile_func_enter>
>
> 25d0: ebfebl 0 <__cyg_profile_func_exit>
>
> 25e8: ebfebl 0 <__cyg_profile_func_exit>
>
>
>
> Please help me.
>
> Thanks in Advance,
> Paramesh
>
>
>
>
>
> On Mon, Jul 30, 2018 at 6:50 AM, Geneviève Bastien
> wrote:
>
>> Hi Paramesh,
>>
>>
>> One way to know if your app is really compiled with
>> -finstrument-functions is doing
>>
>>
>> $ objdump -d my_test_app | grep cyg
>>
>> You would typically see something like this:
>>
>> 1250 <__cyg_profile_func_enter@plt>:
>> 1250:ff 25 fa 2d 20 00jmpq *0x202dfa(%rip)#
>> 204050 <__cyg_profile_func_enter@GLIBC_2.2.5>
>> <__cyg_profile_func_enter@GLIBC_2.2.5>
>> 1260 <__cyg_profile_func_exit@plt>:
>> 1260:ff 25 f2 2d 20 00jmpq *0x202df2(%rip)#
>> 204058 <__cyg_profile_func_exit@GLIBC_2.2.5>
>> <__cyg_profile_func_exit@GLIBC_2.2.5>
>> 14a8:e8 a3 fd ff ff callq 1250
>> <__cyg_profile_func_enter@plt>
>> 16d8:e8 83 fb ff ff callq 1260
>> <__cyg_profile_func_exit@plt>
>> 19c5:e8 86 f8 ff ff callq 1250
>> <__cyg_profile_func_enter@plt>
>> 19e2:e9 79 f8 ff ff jmpq 1260
>> <__cyg_profile_func_exit@plt>
>> 1a0d:e8 3e f8 ff ff callq 1250
>> <__cyg_profile_func_enter@plt>
>>
>> If you see nothing, as Mathieu said, you can check the individual make
>> commands and see what flags are being used on the command line.
>>
>> Geneviève
>>
>>
>>
>> On 2018-07-29 09:29 PM, paramesh p wrote:
>>
>> Hi,
>>I am trying to use Function Tracing for my application running in
>> 32-bit ARM Platform. I have added below lines in my makefile for enabling
>> Trace Data for function tracing
>>
>> AM_CFLAGS += -g -O0 -finstrument-functions
>> AM_CXXFLAGS += -g -O0 -finstrument-functions
>>
>> **(My App have both C && CPP files, So I added CFLAGS & CXXFLAGS).
>>
>> I am running below commands,
>> $lttng create session1
>> $lttng enable-event -u -a --loglevel-only TRACE_DEBUG_FUNCTION
>> $lttng start
>> $LD_PRELOAD=liblttng-ust-cyg-profile.so.0.0.0 my_test_app
>> $lttng start
>> $babeltrace /home/root/lttng-traces/session1
>>
>> Its showing nothing.
>>
>> I tried with below event-enable command also. There is no data
>> $lttng enable-event -u -a --loglevel TRACE_DEBUG_FUNCTION
>>
>> But If I use the command, "lttng enable-event -u -a" for enabling the
>> event, I am getting below output from babeltrace,
>>
>> [22:25:30.812389281] (+?.?) ZZZ ust_baddr_statedump:soinfo: {
>> cpu_id = 1 }, { baddr = 0xAD1A9000, sopath =
>> "/usr/lib/liblttng-ust-cyg-profile.so.0.0.0",
>> size = 10004, mtime = 1532324280 }
>> [22:25:30.812496469] (+0.000107188) ZZZ ust_baddr_statedump:soinfo: {
>> cpu_id = 1 }, { baddr = 0x4DFF, sopath = "/usr/lib/xxx.so", size =
>> 19540, mtime = 1532369202 }
>> [22:25:30.812604177] (+0.000107708) ZZZ ust_baddr_statedump:soinfo: {
>> cpu_id = 1 }, { baddr = 0x4E12, sopath = "/usr/lib/libcutils.so.0.0.0",
>> size = 48624, mtime =
Re: [lttng-dev] Function Tracing Fails
Sorry for the delayed response,
@Mathieu,
I have attached the build log. The Project I am working is Yocto
Project based build system. My App uses the shared object "libhw.so". So,
it built first. As I said before,below are the flag I added
AM_CFLAGS += -g -O0 -finstrument-functions
AM_CXXFLAGS += -g -O0 -finstrument-functions
From the log I found that "-finstrument-functions" flag included in
compiling all the source files, ' libhw.la' file and 'my_test_app'
binary, but not included for compiling 'libhw.so'. I am not sure why? My
question is, as you see my shared object and binary includes following so's
"libtinyalsa.so libexpat.so libbinder.so libutils.so libhwwrapper.so
libhardware.so libcutils.so liblog.so". Are all these need to be compiled
with finstrument flag. In that case, it will increase my workload, since
some of them are custom build and some from the libs and each of them might
have their own dependents.
@gen,
objdump doesn't support arm architecture. So, I used
"arm-linux-gnueabi-objdump" tool. I could see cyg information to all my
object files but I could not see for "libhw.so" and "my_test_app" files.
cyg information of one of my source file,
$ arm-linux-gnueabi-objdump -d libhw_la-hw_api.o | grep cyg
20: ebfebl 0 <__cyg_profile_func_enter>
30: eafeb 0 <__cyg_profile_func_exit>
64: ebfebl 0 <__cyg_profile_func_enter>
a4: ebfebl 0 <__cyg_profile_func_exit>
.
.
2548: ebfebl 0 <__cyg_profile_func_exit>
258c: ebfebl 0 <__cyg_profile_func_enter>
25d0: ebfebl 0 <__cyg_profile_func_exit>
25e8: ebfebl 0 <__cyg_profile_func_exit>
Please help me.
Thanks in Advance,
Paramesh
On Mon, Jul 30, 2018 at 6:50 AM, Geneviève Bastien
wrote:
> Hi Paramesh,
>
>
> One way to know if your app is really compiled with -finstrument-functions
> is doing
>
>
> $ objdump -d my_test_app | grep cyg
>
> You would typically see something like this:
>
> 1250 <__cyg_profile_func_enter@plt>:
> 1250:ff 25 fa 2d 20 00jmpq *0x202dfa(%rip)#
> 204050 <__cyg_profile_func_enter@GLIBC_2.2.5>
> <__cyg_profile_func_enter@GLIBC_2.2.5>
> 1260 <__cyg_profile_func_exit@plt>:
> 1260:ff 25 f2 2d 20 00jmpq *0x202df2(%rip)#
> 204058 <__cyg_profile_func_exit@GLIBC_2.2.5>
> <__cyg_profile_func_exit@GLIBC_2.2.5>
> 14a8:e8 a3 fd ff ff callq 1250
> <__cyg_profile_func_enter@plt>
> 16d8:e8 83 fb ff ff callq 1260
> <__cyg_profile_func_exit@plt>
> 19c5:e8 86 f8 ff ff callq 1250
> <__cyg_profile_func_enter@plt>
> 19e2:e9 79 f8 ff ff jmpq 1260
> <__cyg_profile_func_exit@plt>
> 1a0d:e8 3e f8 ff ff callq 1250
> <__cyg_profile_func_enter@plt>
>
> If you see nothing, as Mathieu said, you can check the individual make
> commands and see what flags are being used on the command line.
>
> Geneviève
>
>
>
> On 2018-07-29 09:29 PM, paramesh p wrote:
>
> Hi,
>I am trying to use Function Tracing for my application running in
> 32-bit ARM Platform. I have added below lines in my makefile for enabling
> Trace Data for function tracing
>
> AM_CFLAGS += -g -O0 -finstrument-functions
> AM_CXXFLAGS += -g -O0 -finstrument-functions
>
> **(My App have both C && CPP files, So I added CFLAGS & CXXFLAGS).
>
> I am running below commands,
> $lttng create session1
> $lttng enable-event -u -a --loglevel-only TRACE_DEBUG_FUNCTION
> $lttng start
> $LD_PRELOAD=liblttng-ust-cyg-profile.so.0.0.0 my_test_app
> $lttng start
> $babeltrace /home/root/lttng-traces/session1
>
> Its showing nothing.
>
> I tried with below event-enable command also. There is no data
> $lttng enable-event -u -a --loglevel TRACE_DEBUG_FUNCTION
>
> But If I use the command, "lttng enable-event -u -a" for enabling the
> event, I am getting below output from babeltrace,
>
> [22:25:30.812389281] (+?.?) ZZZ ust_baddr_statedump:soinfo: {
> cpu_id = 1 }, { baddr = 0xAD1A9000, sopath =
> "/usr/lib/liblttng-ust-cyg-profile.so.0.0.0",
> size = 10004, mtime = 1532324280 }
> [22:25:30.812496469] (+0.000107188) ZZZ ust_baddr_statedump:soinfo: {
> cpu_id = 1 }, { baddr = 0x4DFF, sopath = "/usr/lib/xxx.so", size =
> 19540, mtime = 1532369202 }
> [22:25:30.812604177] (+0.000107708) ZZZ ust_baddr_statedump:soinfo: {
> cpu_id = 1 }, { baddr = 0x4E12, sopath = "/usr/lib/libcutils.so.0.0.0",
> size = 48624, mtime = 1532323462 }
> [22:25:30.812655219] (+0.51042) ZZZ ust_baddr_statedump:soinfo: {
> cpu_id = 1 }, { baddr = 0x4DC8, sopath = "/lib/libpthread-2.22.so",
> size = 94976, mtime = 1532322845 }
> [22:25:30.812701677] (+0.46458) ZZZ ust_baddr_statedump:soinfo: {
> cpu_id = 1 }, { baddr =
Re: [lttng-dev] Function Tracing Fails
Hi Paramesh,
One way to know if your app is really compiled with
-finstrument-functions is doing
$ objdump -d my_test_app | grep cyg
You would typically see something like this:
1250 <__cyg_profile_func_enter@plt>:
1250: ff 25 fa 2d 20 00 jmpq *0x202dfa(%rip) #
204050 <__cyg_profile_func_enter@GLIBC_2.2.5>
1260 <__cyg_profile_func_exit@plt>:
1260: ff 25 f2 2d 20 00 jmpq *0x202df2(%rip) #
204058 <__cyg_profile_func_exit@GLIBC_2.2.5>
14a8: e8 a3 fd ff ff callq 1250
<__cyg_profile_func_enter@plt>
16d8: e8 83 fb ff ff callq 1260
<__cyg_profile_func_exit@plt>
19c5: e8 86 f8 ff ff callq 1250
<__cyg_profile_func_enter@plt>
19e2: e9 79 f8 ff ff jmpq 1260
<__cyg_profile_func_exit@plt>
1a0d: e8 3e f8 ff ff callq 1250
<__cyg_profile_func_enter@plt>
If you see nothing, as Mathieu said, you can check the individual make
commands and see what flags are being used on the command line.
Geneviève
On 2018-07-29 09:29 PM, paramesh p wrote:
> Hi,
> I am trying to use Function Tracing for my application running in
> 32-bit ARM Platform. I have added below lines in my makefile for
> enabling Trace Data for function tracing
>
> AM_CFLAGS += -g -O0 -finstrument-functions
> AM_CXXFLAGS += -g -O0 -finstrument-functions
>
> **(My App have both C && CPP files, So I added CFLAGS & CXXFLAGS).
>
> I am running below commands,
> $lttng create session1
> $lttng enable-event -u -a --loglevel-only TRACE_DEBUG_FUNCTION
> $lttng start
> $LD_PRELOAD=liblttng-ust-cyg-profile.so.0.0.0 my_test_app
> $lttng start
> $babeltrace /home/root/lttng-traces/session1
>
> Its showing nothing.
>
> I tried with below event-enable command also. There is no data
> $lttng enable-event -u -a --loglevel TRACE_DEBUG_FUNCTION
>
> But If I use the command, "lttng enable-event -u -a" for enabling the
> event, I am getting below output from babeltrace,
>
> [22:25:30.812389281] (+?.?) ZZZ ust_baddr_statedump:soinfo: {
> cpu_id = 1 }, { baddr = 0xAD1A9000, sopath =
> "/usr/lib/liblttng-ust-cyg-profile.so.0.0.0", size = 10004, mtime =
> 1532324280 }
> [22:25:30.812496469] (+0.000107188) ZZZ ust_baddr_statedump:soinfo: {
> cpu_id = 1 }, { baddr = 0x4DFF, sopath = "/usr/lib/xxx.so", size =
> 19540, mtime = 1532369202 }
> [22:25:30.812604177] (+0.000107708) ZZZ ust_baddr_statedump:soinfo: {
> cpu_id = 1 }, { baddr = 0x4E12, sopath =
> "/usr/lib/libcutils.so.0.0.0", size = 48624, mtime = 1532323462 }
> [22:25:30.812655219] (+0.51042) ZZZ ust_baddr_statedump:soinfo: {
> cpu_id = 1 }, { baddr = 0x4DC8, sopath = "/lib/libpthread-2.22.so
> ", size = 94976, mtime = 1532322845 }
> [22:25:30.812701677] (+0.46458) ZZZ ust_baddr_statedump:soinfo: {
> cpu_id = 1 }, { baddr = 0x4DB2, sopath = "/lib/libc-2.22.so
> ", size = 1304484, mtime = 1532322845 }
> [22:25:30.812757927] (+0.56250) ZZZ ust_baddr_statedump:soinfo: {
> cpu_id = 1 }, { baddr = 0xAD15B000, sopath =
> "/usr/lib/liblttng-ust.so.0.0.0", size = 315248, mtime = 1532324280 }
> [22:25:30.812814229] (+0.56302) ZZZ ust_baddr_statedump:soinfo: {
> cpu_id = 1 }, { baddr = 0xAD149000, sopath =
> "/usr/lib/liblttng-ust-tracepoint.so.0.0.0", size = 35624, mtime =
> 1532324280 }
> [22:25:30.812860635] (+0.46406) ZZZ ust_baddr_statedump:soinfo: {
> cpu_id = 1 }, { baddr = 0x4DEC, sopath = "/lib/librt-2.22.so
> ", size = 28380, mtime = 1532322845 }
> [22:25:30.812904438] (+0.43803) ZZZ ust_baddr_statedump:soinfo: {
> cpu_id = 1 }, { baddr = 0x4DCB, sopath = "/lib/libdl-2.22.so
> ", size = 11236, mtime = 1532322845 }
> [22:25:30.812959125] (+0.54687) ZZZ ust_baddr_statedump:soinfo: {
> cpu_id = 1 }, { baddr = 0x4DE1, sopath =
> "/usr/lib/liburcu-bp.so.2.0.0", size = 29052, mtime = 1532323584 }
> [22:25:30.813013969] (+0.54844) ZZZ ust_baddr_statedump:soinfo: {
> cpu_id = 1 }, { baddr = 0x4DE0, sopath =
> "/usr/lib/liburcu-cds.so.2.0.0", size = 26152, mtime = 1532323584 }
> [22:25:30.813485479] (+0.000471510) ZZZ ust_baddr_statedump:soinfo: {
> cpu_id = 1 }, { baddr = 0x4DD6, sopath =
> "/usr/lib/liburcu-common.so.2.0.0", size = 13084, mtime = 1532323584 }
> [22:25:30.813600792] (+0.000115313) ZZZ ust_baddr_statedump:soinfo: {
> cpu_id = 1 }, { baddr = 0x4DAE, sopath = "/lib/ld-2.22.so
> ", size = 139632, mtime = 1532322845 }
> [22:25:30.813663656] (+0.62864) ZZZ ust_baddr_statedump:soinfo: {
> cpu_id = 1 }, { baddr = 0x4DFC, sopath = "/usr/lib/xxx.so.1.0.0",
> size = 19456, mtime = 1532323510 }
> [22:25:30.813720635] (+0.56979) ZZZ ust_baddr_statedump:soinfo: {
> cpu_id = 1 }, { baddr = 0x4E03, sopath = "/usr/lib/xxx.so.1.6.0",
> size = 142164, mtime = 1532323441 }
> [22:25:30.813776990] (+0.56355) ZZZ ust_baddr_statedump:soinfo: {
> cpu_id = 1 }, {
Re: [lttng-dev] Function Tracing Fails
- On Jul 29, 2018, at 9:29 PM, paramesh p wrote:
> Hi,
> I am trying to use Function Tracing for my application running in 32-bit ARM
> Platform. I have added below lines in my makefile for enabling Trace Data for
> function tracing
> AM_CFLAGS += -g -O0 -finstrument-functions
> AM_CXXFLAGS += -g -O0 -finstrument-functions
> **(My App have both C && CPP files, So I added CFLAGS & CXXFLAGS).
> I am running below commands,
> $lttng create session1
> $lttng enable-event -u -a --loglevel-only TRACE_DEBUG_FUNCTION
> $lttng start
> $LD_PRELOAD=liblttng-ust-cyg-profile.so.0.0.0 my_test_app
> $lttng start
> $babeltrace /home/root/lttng-traces/session1
> Its showing nothing.
> I tried with below event-enable command also. There is no data
> $lttng enable-event -u -a --loglevel TRACE_DEBUG_FUNCTION
> But If I use the command, "lttng enable-event -u -a" for enabling the event, I
> am getting below output from babeltrace,
> [22:25:30.812389281] (+?.?) ZZZ ust_baddr_statedump:soinfo: { cpu_id
> = 1
> }, { baddr = 0xAD1A9000, sopath =
> "/usr/lib/liblttng-ust-cyg-profile.so.0.0.0",
> size = 10004, mtime = 1532324280 }
> [22:25:30.812496469] (+0.000107188) ZZZ ust_baddr_statedump:soinfo: { cpu_id
> = 1
> }, { baddr = 0x4DFF, sopath = "/usr/lib/xxx.so", size = 19540, mtime =
> 1532369202 }
> [22:25:30.812604177] (+0.000107708) ZZZ ust_baddr_statedump:soinfo: { cpu_id
> = 1
> }, { baddr = 0x4E12, sopath = "/usr/lib/libcutils.so.0.0.0", size = 48624,
> mtime = 1532323462 }
> [22:25:30.812655219] (+0.51042) ZZZ ust_baddr_statedump:soinfo: { cpu_id
> = 1
> }, { baddr = 0x4DC8, sopath = "/lib/ [ http://libpthread-2.22.so/ |
> libpthread-2.22.so ] ", size = 94976, mtime = 1532322845 }
> [22:25:30.812701677] (+0.46458) ZZZ ust_baddr_statedump:soinfo: { cpu_id
> = 1
> }, { baddr = 0x4DB2, sopath = "/lib/ [ http://libc-2.22.so/ | libc-2.22.so
> ] ", size = 1304484, mtime = 1532322845 }
> [22:25:30.812757927] (+0.56250) ZZZ ust_baddr_statedump:soinfo: { cpu_id
> = 1
> }, { baddr = 0xAD15B000, sopath = "/usr/lib/liblttng-ust.so.0.0.0", size =
> 315248, mtime = 1532324280 }
> [22:25:30.812814229] (+0.56302) ZZZ ust_baddr_statedump:soinfo: { cpu_id
> = 1
> }, { baddr = 0xAD149000, sopath = "/usr/lib/liblttng-ust-tracepoint.so.0.0.0",
> size = 35624, mtime = 1532324280 }
> [22:25:30.812860635] (+0.46406) ZZZ ust_baddr_statedump:soinfo: { cpu_id
> = 1
> }, { baddr = 0x4DEC, sopath = "/lib/ [ http://librt-2.22.so/ |
> librt-2.22.so ] ", size = 28380, mtime = 1532322845 }
> [22:25:30.812904438] (+0.43803) ZZZ ust_baddr_statedump:soinfo: { cpu_id
> = 1
> }, { baddr = 0x4DCB, sopath = "/lib/ [ http://libdl-2.22.so/ |
> libdl-2.22.so ] ", size = 11236, mtime = 1532322845 }
> [22:25:30.812959125] (+0.54687) ZZZ ust_baddr_statedump:soinfo: { cpu_id
> = 1
> }, { baddr = 0x4DE1, sopath = "/usr/lib/liburcu-bp.so.2.0.0", size =
> 29052,
> mtime = 1532323584 }
> [22:25:30.813013969] (+0.54844) ZZZ ust_baddr_statedump:soinfo: { cpu_id
> = 1
> }, { baddr = 0x4DE0, sopath = "/usr/lib/liburcu-cds.so.2.0.0", size =
> 26152, mtime = 1532323584 }
> [22:25:30.813485479] (+0.000471510) ZZZ ust_baddr_statedump:soinfo: { cpu_id
> = 1
> }, { baddr = 0x4DD6, sopath = "/usr/lib/liburcu-common.so.2.0.0", size =
> 13084, mtime = 1532323584 }
> [22:25:30.813600792] (+0.000115313) ZZZ ust_baddr_statedump:soinfo: { cpu_id
> = 1
> }, { baddr = 0x4DAE, sopath = "/lib/ [ http://ld-2.22.so/ | ld-2.22.so ]
> ",
> size = 139632, mtime = 1532322845 }
> [22:25:30.813663656] (+0.62864) ZZZ ust_baddr_statedump:soinfo: { cpu_id
> = 1
> }, { baddr = 0x4DFC, sopath = "/usr/lib/xxx.so.1.0.0", size = 19456, mtime
> = 1532323510 }
> [22:25:30.813720635] (+0.56979) ZZZ ust_baddr_statedump:soinfo: { cpu_id
> = 1
> }, { baddr = 0x4E03, sopath = "/usr/lib/xxx.so.1.6.0", size = 142164,
> mtime
> = 1532323441 }
> [22:25:30.813776990] (+0.56355) ZZZ ust_baddr_statedump:soinfo: { cpu_id
> = 1
> }, { baddr = 0x4E06, sopath = "/usr/lib/xxx.so.0.0.0", size = 265304,
> mtime
> = 1532324468 }
> [22:25:30.813843917] (+0.66927) ZZZ ust_baddr_statedump:soinfo: { cpu_id
> = 1
> }, { baddr = 0x4DEA, sopath = "/usr/lib/xxx.so.0.0.0", size = 84016, mtime
> = 1532324363 }
> [22:25:30.813884385] (+0.40468) ZZZ ust_baddr_statedump:soinfo: { cpu_id
> = 1
> }, { baddr = 0x4DFE, sopath = "/usr/lib/xxx.so", size = 34204, mtime =
> 1532324426 }
> [22:25:30.813940479] (+0.56094) ZZZ ust_baddr_statedump:soinfo: { cpu_id
> = 1
> }, { baddr = 0x4DFD, sopath = "/usr/lib/xxx.so", size = 7388, mtime =
> 1532324388 }
> [22:25:30.813993604] (+0.53125) ZZZ ust_baddr_statedump:soinfo: { cpu_id
> = 1
> }, { baddr = 0x4E00, sopath = "/usr/lib/xxx.so", size = 33152, mtime =
> 1532323414 }
> [22:25:30.814049333] (+0.55729) ZZZ ust_baddr_statedump:soinfo: { cpu_id
> = 1
> }, { baddr = 0x4DEE, sopath = "/usr/lib/libstdc++.so.6.0.20", size =
>
