Hi David,

I'm using
Version: 4.5.1
Build id: I20090224

The decoder seems to use 8 bytes for addr and len, so addr swallows the dword for len, and len mistakes the first 8 
bytes of the name.

This is the raw data (from the raw data view in IDE):
                       My guess:
0x05 0x20 0x00 0x00   pid (0x2005 = 8197)
0x00 0x10 0x30 0x70   addr (0x70301000)
0x88 0x31 0x06 0x00   len (0x63188 = 405896)
0x6C 0x64 0x71 0x6E   name 'ldqn'
0x78 0x2E 0x73 0x6F        'x.so'
0x2E 0x32 0x00 0x00        '.2'

This is the decoded data:
Key, 	Value
addr, 	0x6318870301000
len, 	8030813655315604588
name, 	.2
pid, 	8197
process, slogger 

Trace properties:
       TRACE_FILE_NAME:: /dev/shmem/tracebuffer.kev
            TRACE_DATE:: Thu Jan  1 00:00:00 1970
       TRACE_VER_MAJOR:: 1
       TRACE_VER_MINOR:: 01
   TRACE_LITTLE_ENDIAN:: TRUE
        TRACE_ENCODING:: 16 byte events
       TRACE_BOOT_DATE:: Thu Jan  1 00:00:00 1970
  TRACE_CYCLES_PER_SEC:: 12375000
         TRACE_CPU_NUM:: 1
         TRACE_SYSNAME:: QNX
        TRACE_NODENAME:: dcw221mopftarget
     TRACE_SYS_RELEASE:: 6.3.2
     TRACE_SYS_VERSION:: 2009/02/11-15:53:32EST
         TRACE_MACHINE:: HB_SH7785
     TRACE_SYSPAGE_LEN:: 1776

traceprinter decodes the event correctly.

I suppose it is a bug in my IDE decoder.

Thanks,
Daniel

>-----Ursprüngliche Nachricht-----
>Von: David Cummings [mailto:community-noreply@qnx.com] 
>Gesendet: Donnerstag, 30. Juli 2009 15:51
>An: general-ide
>Betreff: Re: AW: System Profiler: bad event decoding for MMap Name
>
>Hi Daniel,
>
>> The decoding for this event is crap, probably a copy&paste error...
>I've tested a couple of kevs with mmap name events and they 
>are all appearing properly decoded in the IDE. Which version 
>of IDE are you using? What is traceprinter outputting for your 
>mmap name events? Could you send me a copy of your kev to investigate?
>
>Yes, there is is a typo with the MUnmap events in the IDE. 
>They appear correctly in traceprinter's output. I've raised a 
>PR to fix this spelling.
>
>Thanks,
>David
>
>> The raw event data seems to contain the correct name, but 
>the decoding 
>> messes it up. ?
>> 
>> Let's see what the IDE folks will say.
>> 
>> Regards,
>> Daniel
>> 
>> >-----Ursprüngliche Nachricht-----
>> >Von: Malte Mundt [mailto:community-noreply@qnx.com]
>> >Gesendet: Donnerstag, 30. Juli 2009 14:09
>> >An: general-ide
>> >Betreff: Re: System Profiler: bad event decoding for MMap Name
>> >
>> >Hi Daniel,
>> >
>> >> While writing a reporting tool for MMap / MMUnmap I came 
>across the 
>> >> 'MMap Name' events. They seem to get 'misunderpreted'. Here
>> >is an example:
>> >
>> >> Q: What are these messages for? what kind of data are the
>> >supposed to show?
>> >> Apparently, MMap Name is the result of a debug_info call -
>> >whatever that is.
>> >
>> >I understand the 'MAPNAME' events happens when someone is loading a 
>> >DLL that is not automatically loaded when starting the program. So 
>> >MAPNAME shows up when dlopen() gets called to load a shared object.
>> >
>> >As for the values, I *believe* the meanings are as follows:
>> >
>> >> Key, Value
>> >> addr, 0xf6aab8200000
>> >This should be the virtual address where the shared object is being 
>> >loaded to.
>> >
>> >> len, 7598523844058834276
>> >This should be the length of the shared object (seems a bit high 
>> >number though...)
>> >
>> >> name, x.so
>> >The name of the shared object being...