TeamForge : Post

Forum Topic - rmat file size limit: (14 Items)

View: as

Rex Lam

08/12/2009 7:18 PM

post35863

It appears that the .rmat file generated by the memory analysis tool has a size limit of a signed long (2147483647).  
After this limit is reached, I cannot export memory events any longer.  Are events or bin snapshots still captured when 
the file has reached the limit?  Are older events removed from the file?  Or is the file size limit a bug?

My set up includes Momentics IDE 4.6 (Build id: I20090510), which I use with QNX 6.3.2a on my target.  I have a version 
of qconn and librcheck.so that works with this IDE.  

Please let me know if there is a fix for this issue.

Elena Laskavaia

08/13/2009 12:39 PM

post35934

Re: rmat file size limit

there is no fix for size limit but there is alternative way for 
capturing data - using qconn buffer. Switch to use device instead of 
file in the advanced mat settings. You need latest qconn for that.
Also 2G+ of data would be not that usefull in IDE anyway. Try to limit 
data capture using mat options or programmatically by enabling/disabling 
tracing from the code (I believe I sent you an API).

Rex Lam wrote:
> It appears that the .rmat file generated by the memory analysis tool has a size limit of a signed long (2147483647).  
After this limit is reached, I cannot export memory events any longer.  Are events or bin snapshots still captured when 
the file has reached the limit?  Are older events removed from the file?  Or is the file size limit a bug?
>
> My set up includes Momentics IDE 4.6 (Build id: I20090510), which I use with QNX 6.3.2a on my target.  I have a 
version of qconn and librcheck.so that works with this IDE.  
>
> Please let me know if there is a fix for this issue.
>
>
>
> _______________________________________________
>
> QNX Momentics Community Support
> http://community.qnx.com/sf/go/post35863
>
>

Rex Lam

08/13/2009 1:10 PM

post35936

Re: rmat file size limit

Is the latest qconn available for 6.3.2?

With big memory leaks, it is easy to detect without having the rmat file grow too big.  I am looking into small leaks 
now.  These leaks occur over a really long period of time.  Since I cannot tell when the leak will occur, I have to 
capture continuous traces.  I have already tried disabling all unnecessary mat options, but I need a complete backtrace 
so the file grows quite quickly.  I will switch to device and try again after I get the latest qconn.  Please let me 
know where I can get one that runs on 6.3.2.

Andy Jin(deleted)

08/13/2009 1:19 PM

post35941

Re: rmat file size limit

Hi, Rex,

I just posted the latest IDE 4.7 on our F27 download site

http://community.qnx.com/sf/frs/do/listReleases/projects.ide/frs.ide_4_7

It contains qconn patch to 6.3.2. If you can run this version of IDE 
with your 6.3.2 Momentics, you can select from "Help -> Software Updates 
-> qconn updates". IDE will handle updating your 6.3.2 qconn to the 
latest version. You can transfer the qconn binary from your $QNX_TARGET 
to your remote target.

Let me know if you can't run IDE 4.7. I can extract the qconn patch from 
it and post it separately. But you have to install it by yourself.

- Andy

Rex Lam wrote:
> Is the latest qconn available for 6.3.2?
>
> With big memory leaks, it is easy to detect without having the rmat file grow too big.  I am looking into small leaks 
now.  These leaks occur over a really long period of time.  Since I cannot tell when the leak will occur, I have to 
capture continuous traces.  I have already tried disabling all unnecessary mat options, but I need a complete backtrace 
so the file grows quite quickly.  I will switch to device and try again after I get the latest qconn.  Please let me 
know where I can get one that runs on 6.3.2.
>
>
>
> _______________________________________________
>
> QNX Momentics Community Support
> http://community.qnx.com/sf/go/post35936
>
>

Rex Lam

08/13/2009 1:26 PM

post35944

Re: rmat file size limit

Thanks Andy.  I will give that a try.

Elena Laskavaia

08/13/2009 3:18 PM

post35954

Re: rmat file size limit

You don't need IDE 4.7 for that. I think qconn that posted on foundry is 
sufficient. IDE 4.7 has new UI for MAT tools and has not been tested yet.

Rex Lam wrote:
> Thanks Andy.  I will give that a try.
>
>
>
> _______________________________________________
>
> QNX Momentics Community Support
> http://community.qnx.com/sf/go/post35944
>
>

Rex Lam

08/13/2009 4:10 PM

post35956

Re: rmat file size limit

I am still downloading IDE 4.7 which has the new qconn.  It is taking a while.  If you have a direct link to the new 
qconn that works on 6.3.2, please let me know where it is.  I tried searching for it, but I could not find it.  I will 
try IDE 4.6 with the new qconn first, once I have it.

Andy Jin(deleted)

08/13/2009 4:24 PM

post35957

Re: rmat file size limit

Get the 6.3.2 qconn patch from here 
http://community.qnx.com/sf/frs/do/viewRelease/projects.ide/frs.ide_4_7.ide_4_7_20090805
Download the "patch-632-1437-qconn-460.tar". You need to manually 
extract the binaries from it.

Rex Lam wrote:
> I am still downloading IDE 4.7 which has the new qconn.  It is taking a while.  If you have a direct link to the new 
qconn that works on 6.3.2, please let me know where it is.  I tried searching for it, but I could not find it.  I will 
try IDE 4.6 with the new qconn first, once I have it.
>
>
>
> _______________________________________________
>
> QNX Momentics Community Support
> http://community.qnx.com/sf/go/post35956
>
>

Rex Lam

08/13/2009 4:27 PM

post35958

Re: rmat file size limit

Awesome.  I have it now and will try it.  Thank you.

Andy Jin(deleted)

08/13/2009 4:37 PM

post35959

Re: rmat file size limit

Good. I have moved the two patches to its formal download area 
http://community.qnx.com/sf/frs/do/listReleases/projects.ide/frs.binary_patches_for_ide

Rex Lam wrote:
> Awesome.  I have it now and will try it.  Thank you.
>
>
>
> _______________________________________________
>
> QNX Momentics Community Support
> http://community.qnx.com/sf/go/post35958
>
>

frederic fabbri(deleted)

08/20/2009 5:13 PM

post36391

Re: rmat file size limit

I tried the streaming device option to overcome the file size limitation but it does not seem to work.  I use IDE 4.6.0 
I20090510 with the updated Qconn you posted. Here is what happens once I click on "get snapshots" and then export bin 
events:

-The exported csv data is empty.
-The gauge at the bottom right of the IDE "Dump Snapshot" never seems to finish (it's been 45min and it is still going)
-The IDE seems to have lost connection with the machine because the target name in the Target File System Navigator 
window has a red dot.

Note: I launched the project via the run Configuration window with the following parameters:

Memory Errors: Disabled
Memory Tacing: Disabled
Memory Snapshots: Enabled:
   - Perform Snashopt every : 100H
   - bins Counters: Default
Adcanced Settings:
  - Runtime Library: librcheck.so
  - Use streaming device: /dev/rcheck/traces.rmat
  - Create control thread: Enabled
  - Show Debug output on console: Enabled

Elena Laskavaia

08/22/2009 4:33 PM

post36472

Re: rmat file size limit

Are you running it in debug mode or in run mode? Can you just try memory 
leak example shipped with IDE with your settings on your target to see 
it if works?

frederic fabbri wrote:
> I tried the streaming device option to overcome the file size limitation but it does not seem to work.  I use IDE 4.6.
0 I20090510 with the updated Qconn you posted. Here is what happens once I click on "get snapshots" and then export bin 
events:
>
> -The exported csv data is empty.
> -The gauge at the bottom right of the IDE "Dump Snapshot" never seems to finish (it's been 45min and it is still 
going)
> -The IDE seems to have lost connection with the machine because the target name in the Target File System Navigator 
window has a red dot.
>
> Note: I launched the project via the run Configuration window with the following parameters:
>
> Memory Errors: Disabled
> Memory Tacing: Disabled
> Memory Snapshots: Enabled:
>    - Perform Snashopt every : 100H
>    - bins Counters: Default
> Adcanced Settings:
>   - Runtime Library: librcheck.so
>   - Use streaming device: /dev/rcheck/traces.rmat
>   - Create control thread: Enabled
>   - Show Debug output on console: Enabled
>
>
>
>
> _______________________________________________
>
> QNX Momentics Community Support
> http://community.qnx.com/sf/go/post36391
>
>

frederic fabbri(deleted)

08/24/2009 11:55 AM

post36536

Re: rmat file size limit

> Are you running it in debug mode or in run mode? 

Yes I'm running in run mode; I stated that in my original post, see below:
> > frederic fabbri wrote:
> > Note: I launched the project via the run Configuration window with ... 


> Can you just try memory 
> leak example shipped with IDE with your settings on your target to see 
> it if works?
> 

When I switch my setting from "Use streaming device" to "Use regular file" it works perfectly; expect that the rmat 
file's size max out at 2G.

Elena Laskavaia

08/26/2009 10:42 AM

post36708

Re: rmat file size limit

I guess something is not working... You can also try to use pipe - 
create a pipe file on target and use its name instead of regular file.
Unfortunately you cannot use  control thread in this mode because it 
would create dead locks, but if you can call for memory leaks dump using 
API from the program it should work.

frederic fabbri wrote:
>> Are you running it in debug mode or in run mode? 
>>     
>
> Yes I'm running in run mode; I stated that in my original post, see below:
>   
>>> frederic fabbri wrote:
>>> Note: I launched the project via the run Configuration window with ... 
>>>       
>
>
>   
>> Can you just try memory 
>> leak example shipped with IDE with your settings on your target to see 
>> it if works?
>>
>>     
>
> When I switch my setting from "Use streaming device" to "Use regular file" it works perfectly; expect that the rmat 
file's size max out at 2G.
>
>
>
> _______________________________________________
>
> QNX Momentics Community Support
> http://community.qnx.com/sf/go/post36536
>
>

Return