Project Home
Project Home
Trackers
Trackers
Documents
Documents
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - Profiler strangeness: (24 Items)
   
Profiler strangeness  
This morning I got a profiler session working.  I decided to try it on our target (custom image) to see if it had all 
the required component, could get it to work and couldn't figure out why.  Decided to try back on the devlopment machine
 I had it working on this morning, and no luck.

I'm out of idea.  The IDE is dead silent about what is missing.  All I can get is the Profile session to show the new 
session but the program doesn't show up.  I can see the QPROF_FILE growing on the machine, seems the IDE doesn't see it.
  Yet I'm 100% sure I've specify the same path everywhere.

Trying to get the IDE to give me some clue as to what I'm missing I kill qconn on the target machine.  I could see it 
disappear from the target navigator.  I try to run a profiler session and OMG, it show me a list of process!!!!! At 
first I though I had the wrong target specified and to make sure I deleted all the other target I have.  Try again and 
it still show me a list of processes!!!!! I can see in the top of the windows the name of the target and its the right 
one. It seems to show me the last stuff it go.  If I select a process to profile I get an error "QCONN not found".  I 
restarted qconn, restarted the profile session  and I could see the process list being correctly updated!

But still no go, the Profiler sessions view isn't showing me the process and I have no idea what I'm missing.  It's the 
same executable as I used this morning!  Using Fonctions Instrumentation.
Re: Profiler strangeness  
Not sure what you doing. I am going to guess you steps here, correct me if I am wrong.

a) You compiled you binary/library with Profiling FI (Function Instrumentation)
b) You run your binary from IDE and in Tools tab of launch you enabled Single Application - Function Instrumentation 
combo. As data transfer you selected Update while running.
c) Profiling session shows up and Execution time view is open, but does not show anything?

Or you using profile attach? Not sure where do you see list of processes.


Mario Charest wrote:
> This morning I got a profiler session working.  I decided to try it on our target (custom image) to see if it had all 
the required component, could get it to work and couldn't figure out why.  Decided to try back on the devlopment machine
 I had it working on this morning, and no luck.
> 
> I'm out of idea.  The IDE is dead silent about what is missing.  All I can get is the Profile session to show the new 
session but the program doesn't show up.  I can see the QPROF_FILE growing on the machine, seems the IDE doesn't see it.
  Yet I'm 100% sure I've specify the same path everywhere.
> 
> Trying to get the IDE to give me some clue as to what I'm missing I kill qconn on the target machine.  I could see it 
disappear from the target navigator.  I try to run a profiler session and OMG, it show me a list of process!!!!! At 
first I though I had the wrong target specified and to make sure I deleted all the other target I have.  Try again and 
it still show me a list of processes!!!!! I can see in the top of the windows the name of the target and its the right 
one. It seems to show me the last stuff it go.  If I select a process to profile I get an error "QCONN not found".  I 
restarted qconn, restarted the profile session  and I could see the process list being correctly updated!
> 
> But still no go, the Profiler sessions view isn't showing me the process and I have no idea what I'm missing.  It's 
the same executable as I used this morning!  Using Fonctions Instrumentation.
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post20521
> 
RE: Profiler strangeness  

> -----Original Message-----
> From: Elena Laskavaia [mailto:community-noreply@qnx.com]
> Sent: January-21-09 3:04 PM
> To: general-ide
> Subject: Re: Profiler strangeness
> 
> Not sure what you doing. I am going to guess you steps here, correct me
> if I am wrong.
> 
> a) You compiled you binary/library with Profiling FI (Function
> Instrumentation)

Custom makefile, so added -finstrument-functions and -l profiling.

> b) You run your binary from IDE and in Tools tab of launch you enabled
> Single Application - Function Instrumentation combo. As data transfer
> you selected Update while running.

No I manually launch it and attached afterward.

> c) Profiling session shows up and Execution time view is open, but does
> not show anything?
> 
Yes

> Or you using profile attach? Not sure where do you see list of
> processes.

The list of processes comes up because I'm attaching to it.

> 
> 
> Mario Charest wrote:
> > This morning I got a profiler session working.  I decided to try it
> on our target (custom image) to see if it had all the required
> component, could get it to work and couldn't figure out why.  Decided
> to try back on the devlopment machine I had it working on this morning,
> and no luck.
> >
> > I'm out of idea.  The IDE is dead silent about what is missing.  All
> I can get is the Profile session to show the new session but the
> program doesn't show up.  I can see the QPROF_FILE growing on the
> machine, seems the IDE doesn't see it.  Yet I'm 100% sure I've specify
> the same path everywhere.
> >
> > Trying to get the IDE to give me some clue as to what I'm missing I
> kill qconn on the target machine.  I could see it disappear from the
> target navigator.  I try to run a profiler session and OMG, it show me
> a list of process!!!!! At first I though I had the wrong target
> specified and to make sure I deleted all the other target I have.  Try
> again and it still show me a list of processes!!!!! I can see in the
> top of the windows the name of the target and its the right one. It
> seems to show me the last stuff it go.  If I select a process to
> profile I get an error "QCONN not found".  I restarted qconn, restarted
> the profile session  and I could see the process list being correctly
> updated!
> >
> > But still no go, the Profiler sessions view isn't showing me the
> process and I have no idea what I'm missing.  It's the same executable
> as I used this morning!  Using Fonctions Instrumentation.
> >
> > _______________________________________________
> > General
> > http://community.qnx.com/sf/go/post20521
> >
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post20523
> 
Re: Profiler strangeness  
So you created configuration Profile/Attach to running QNX Process
and you selected Single Application/Function Instrumentation
Your QPROF_FILE matching value of file in attach configuration
and transfer method set to Upload while running? And you running as "Profile" not as "Debug"?

If it still now working try to manually upload file on host and import using Session view, Import command.

Mario Charest wrote:
> 
>> -----Original Message-----
>> From: Elena Laskavaia [mailto:community-noreply@qnx.com]
>> Sent: January-21-09 3:04 PM
>> To: general-ide
>> Subject: Re: Profiler strangeness
>>
>> Not sure what you doing. I am going to guess you steps here, correct me
>> if I am wrong.
>>
>> a) You compiled you binary/library with Profiling FI (Function
>> Instrumentation)
> 
> Custom makefile, so added -finstrument-functions and -l profiling.
> 
>> b) You run your binary from IDE and in Tools tab of launch you enabled
>> Single Application - Function Instrumentation combo. As data transfer
>> you selected Update while running.
> 
> No I manually launch it and attached afterward.
> 
>> c) Profiling session shows up and Execution time view is open, but does
>> not show anything?
>>
> Yes
> 
>> Or you using profile attach? Not sure where do you see list of
>> processes.
> 
> The list of processes comes up because I'm attaching to it.
> 
>>
>> Mario Charest wrote:
>>> This morning I got a profiler session working.  I decided to try it
>> on our target (custom image) to see if it had all the required
>> component, could get it to work and couldn't figure out why.  Decided
>> to try back on the devlopment machine I had it working on this morning,
>> and no luck.
>>> I'm out of idea.  The IDE is dead silent about what is missing.  All
>> I can get is the Profile session to show the new session but the
>> program doesn't show up.  I can see the QPROF_FILE growing on the
>> machine, seems the IDE doesn't see it.  Yet I'm 100% sure I've specify
>> the same path everywhere.
>>> Trying to get the IDE to give me some clue as to what I'm missing I
>> kill qconn on the target machine.  I could see it disappear from the
>> target navigator.  I try to run a profiler session and OMG, it show me
>> a list of process!!!!! At first I though I had the wrong target
>> specified and to make sure I deleted all the other target I have.  Try
>> again and it still show me a list of processes!!!!! I can see in the
>> top of the windows the name of the target and its the right one. It
>> seems to show me the last stuff it go.  If I select a process to
>> profile I get an error "QCONN not found".  I restarted qconn, restarted
>> the profile session  and I could see the process list being correctly
>> updated!
>>> But still no go, the Profiler sessions view isn't showing me the
>> process and I have no idea what I'm missing.  It's the same executable
>> as I used this morning!  Using Fonctions Instrumentation.
>>> _______________________________________________
>>> General
>>> http://community.qnx.com/sf/go/post20521
>>>
>> _______________________________________________
>> General
>> http://community.qnx.com/sf/go/post20523
>>
> 
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post20527
> 
RE: Profiler strangeness  

> -----Original Message-----
> From: Elena Laskavaia [mailto:community-noreply@qnx.com]
> Sent: January-21-09 3:32 PM
> To: general-ide
> Subject: Re: Profiler strangeness
> 
> So you created configuration Profile/Attach to running QNX Process
> and you selected Single Application/Function Instrumentation
> Your QPROF_FILE matching value of file in attach configuration
> and transfer method set to Upload while running?

Yes

> And you running as "Profile" not as "Debug"?

The button says "Profile".

I tried to have the IDE launch the application, that works. Tells me the binary is build the required profiling flags.

> 
> If it still now working try to manually upload file on host and import
> using Session view, Import command.

That works, but I'd like to know why the "live" method isn't working.

What about the process list showing up with contents even if qconn isn't running on the target, that deserve a PR I 
would think.

Darn I forgot to mention I'm using 4.6.0 (I20081216), which by the ways says 4.5.0 on the splash screen.

> 
> Mario Charest wrote:
> >
> >> -----Original Message-----
> >> From: Elena Laskavaia [mailto:community-noreply@qnx.com]
> >> Sent: January-21-09 3:04 PM
> >> To: general-ide
> >> Subject: Re: Profiler strangeness
> >>
> >> Not sure what you doing. I am going to guess you steps here, correct
> me
> >> if I am wrong.
> >>
> >> a) You compiled you binary/library with Profiling FI (Function
> >> Instrumentation)
> >
> > Custom makefile, so added -finstrument-functions and -l profiling.
> >
> >> b) You run your binary from IDE and in Tools tab of launch you
> enabled
> >> Single Application - Function Instrumentation combo. As data
> transfer
> >> you selected Update while running.
> >
> > No I manually launch it and attached afterward.
> >
> >> c) Profiling session shows up and Execution time view is open, but
> does
> >> not show anything?
> >>
> > Yes
> >
> >> Or you using profile attach? Not sure where do you see list of
> >> processes.
> >
> > The list of processes comes up because I'm attaching to it.
> >
> >>
> >> Mario Charest wrote:
> >>> This morning I got a profiler session working.  I decided to try it
> >> on our target (custom image) to see if it had all the required
> >> component, could get it to work and couldn't figure out why.
> Decided
> >> to try back on the devlopment machine I had it working on this
> morning,
> >> and no luck.
> >>> I'm out of idea.  The IDE is dead silent about what is missing.
> All
> >> I can get is the Profile session to show the new session but the
> >> program doesn't show up.  I can see the QPROF_FILE growing on the
> >> machine, seems the IDE doesn't see it.  Yet I'm 100% sure I've
> specify
> >> the same path everywhere.
> >>> Trying to get the IDE to give me some clue as to what I'm missing I
> >> kill qconn on the target machine.  I could see it disappear from the
> >> target navigator.  I try to run a profiler session and OMG, it show
> me
> >> a list of process!!!!! At first I though I had the wrong target
> >> specified and to make sure I deleted all the other target I have.
> Try
> >> again and it still show me a list of processes!!!!! I can see in the
> >> top of the windows the name of the target and its the right one. It
> >> seems to show me the last stuff it go.  If I select a process to
> >> profile I get an error "QCONN not found".  I...
View Full Message
Re: Profiler strangeness  
> That works, but I'd like to know why the "live" method isn't working.
Check the log maybe?
What is the file name you are using? Make sure it is does not have ${random} in it.


> 
> What about the process list showing up with contents even if qconn isn't running on the target, that deserve a PR I 
would think.
It is caching it. I don't think we will fix it. Cache it required because sometime target loosing connection for several
 seconds,
we don't want Target Navigator blink like crazy in this case. As side effect same cache is used in other places...


> 
> Darn I forgot to mention I'm using 4.6.0 (I20081216), which by the ways says 4.5.0 on the splash screen.
Let me check that....
RE: Profiler strangeness  
> >
> > What about the process list showing up with contents even if qconn
> isn't running on the target, that deserve a PR I would think.
> It is caching it. I don't think we will fix it. Cache it required
> because sometime target loosing connection for several seconds,
> we don't want Target Navigator blink like crazy in this case. As side
> effect same cache is used in other places...

It's one thing to use a cache but when the target view shows the target to be disconnected you don't expect a process 
list to show up. Pressing the refresh button should refresh the cache shouldn' it, otherwise what's the point of a 
refresh button.
 
> 
> 
> >
> > Darn I forgot to mention I'm using 4.6.0 (I20081216), which by the
> ways says 4.5.0 on the splash screen.
> Let me check that....
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post20537
> 
Re: Profiler strangeness  
Checked, 4.6 is not working indeed.


Mario Charest wrote:
> 
>> -----Original Message-----
>> From: Elena Laskavaia [mailto:community-noreply@qnx.com]
>> Sent: January-21-09 3:32 PM
>> To: general-ide
>> Subject: Re: Profiler strangeness
>>
>> So you created configuration Profile/Attach to running QNX Process
>> and you selected Single Application/Function Instrumentation
>> Your QPROF_FILE matching value of file in attach configuration
>> and transfer method set to Upload while running?
> 
> Yes
> 
>> And you running as "Profile" not as "Debug"?
> 
> The button says "Profile".
> 
> I tried to have the IDE launch the application, that works. Tells me the binary is build the required profiling flags.

> 
>> If it still now working try to manually upload file on host and import
>> using Session view, Import command.
> 
> That works, but I'd like to know why the "live" method isn't working.
> 
> What about the process list showing up with contents even if qconn isn't running on the target, that deserve a PR I 
would think.
> 
> Darn I forgot to mention I'm using 4.6.0 (I20081216), which by the ways says 4.5.0 on the splash screen.
> 
>> Mario Charest wrote:
>>>> -----Original Message-----
>>>> From: Elena Laskavaia [mailto:community-noreply@qnx.com]
>>>> Sent: January-21-09 3:04 PM
>>>> To: general-ide
>>>> Subject: Re: Profiler strangeness
>>>>
>>>> Not sure what you doing. I am going to guess you steps here, correct
>> me
>>>> if I am wrong.
>>>>
>>>> a) You compiled you binary/library with Profiling FI (Function
>>>> Instrumentation)
>>> Custom makefile, so added -finstrument-functions and -l profiling.
>>>
>>>> b) You run your binary from IDE and in Tools tab of launch you
>> enabled
>>>> Single Application - Function Instrumentation combo. As data
>> transfer
>>>> you selected Update while running.
>>> No I manually launch it and attached afterward.
>>>
>>>> c) Profiling session shows up and Execution time view is open, but
>> does
>>>> not show anything?
>>>>
>>> Yes
>>>
>>>> Or you using profile attach? Not sure where do you see list of
>>>> processes.
>>> The list of processes comes up because I'm attaching to it.
>>>
>>>> Mario Charest wrote:
>>>>> This morning I got a profiler session working.  I decided to try it
>>>> on our target (custom image) to see if it had all the required
>>>> component, could get it to work and couldn't figure out why.
>> Decided
>>>> to try back on the devlopment machine I had it working on this
>> morning,
>>>> and no luck.
>>>>> I'm out of idea.  The IDE is dead silent about what is missing.
>> All
>>>> I can get is the Profile session to show the new session but the
>>>> program doesn't show up.  I can see the QPROF_FILE growing on the
>>>> machine, seems the IDE doesn't see it.  Yet I'm 100% sure I've
>> specify
>>>> the same path everywhere.
>>>>> Trying to get the IDE to give me some clue as to what I'm missing I
>>>> kill qconn on the target machine.  I could see it disappear from the
>>>> target navigator.  I try to run a profiler session and OMG, it show
>> me
>>>> a list of process!!!!! At first I though I had the wrong target
>>>> specified and to make sure I deleted all the other target I have.
>>...
View Full Message
RE: Profiler strangeness  
> -----Original Message-----
> From: Elena Laskavaia [mailto:community-noreply@qnx.com]
> Sent: January-21-09 4:32 PM
> To: general-ide
> Subject: Re: Profiler strangeness
> 
> Checked, 4.6 is not working indeed.
> 
Ok thanks.
> 
> Mario Charest wrote:
> >
> >> -----Original Message-----
> >> From: Elena Laskavaia [mailto:community-noreply@qnx.com]
> >> Sent: January-21-09 3:32 PM
> >> To: general-ide
> >> Subject: Re: Profiler strangeness
> >>
> >> So you created configuration Profile/Attach to running QNX Process
> >> and you selected Single Application/Function Instrumentation
> >> Your QPROF_FILE matching value of file in attach configuration
> >> and transfer method set to Upload while running?
> >
> > Yes
> >
> >> And you running as "Profile" not as "Debug"?
> >
> > The button says "Profile".
> >
> > I tried to have the IDE launch the application, that works. Tells me
> the binary is build the required profiling flags.
> >
> >> If it still now working try to manually upload file on host and
> import
> >> using Session view, Import command.
> >
> > That works, but I'd like to know why the "live" method isn't working.
> >
> > What about the process list showing up with contents even if qconn
> isn't running on the target, that deserve a PR I would think.
> >
> > Darn I forgot to mention I'm using 4.6.0 (I20081216), which by the
> ways says 4.5.0 on the splash screen.
> >
> >> Mario Charest wrote:
> >>>> -----Original Message-----
> >>>> From: Elena Laskavaia [mailto:community-noreply@qnx.com]
> >>>> Sent: January-21-09 3:04 PM
> >>>> To: general-ide
> >>>> Subject: Re: Profiler strangeness
> >>>>
> >>>> Not sure what you doing. I am going to guess you steps here,
> correct
> >> me
> >>>> if I am wrong.
> >>>>
> >>>> a) You compiled you binary/library with Profiling FI (Function
> >>>> Instrumentation)
> >>> Custom makefile, so added -finstrument-functions and -l profiling.
> >>>
> >>>> b) You run your binary from IDE and in Tools tab of launch you
> >> enabled
> >>>> Single Application - Function Instrumentation combo. As data
> >> transfer
> >>>> you selected Update while running.
> >>> No I manually launch it and attached afterward.
> >>>
> >>>> c) Profiling session shows up and Execution time view is open, but
> >> does
> >>>> not show anything?
> >>>>
> >>> Yes
> >>>
> >>>> Or you using profile attach? Not sure where do you see list of
> >>>> processes.
> >>> The list of processes comes up because I'm attaching to it.
> >>>
> >>>> Mario Charest wrote:
> >>>>> This morning I got a profiler session working.  I decided to try
> it
> >>>> on our target (custom image) to see if it had all the required
> >>>> component, could get it to work and couldn't figure out why.
> >> Decided
> >>>> to try back on the devlopment machine I had it working on this
> >> morning,
> >>>> and no luck.
> >>>>> I'm out of idea.  The IDE is dead silent about what is missing.
> >> All
> >>>> I can get is the Profile session to show the new session but the
> >>>> program doesn't show up.  I can see the QPROF_FILE growing...
View Full Message
Re: Profiler strangeness  
On the other hand, I had button "disable automatic refresh" on which prevent refresh (looks like lock).
When I unpress it - it starts refreshing.
Is yours enabled?
RE: Profiler strangeness  
Don't know what button you are talking about? 

> -----Original Message-----
> From: Elena Laskavaia [mailto:community-noreply@qnx.com]
> Sent: January-21-09 5:09 PM
> To: general-ide
> Subject: Re: Profiler strangeness
> 
> On the other hand, I had button "disable automatic refresh" on which
> prevent refresh (looks like lock).
> When I unpress it - it starts refreshing.
> Is yours enabled?
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post20543
> 
Re: Profiler strangeness  
In Execution time view there is a button that looks like "lock" and tooltip says "Prevent auto-refresh" or "Scroll-lock"
.

The other problem may be that qconn does not have enough time slice to transfer the data and it times-out and give up on
 updates.
You can enabled debug tracing (if you want to help to figure it out) by creating a file "options"
---
com.qnx.tools.ide.profiler2.core/debug=false
---
and running qde with extra option
-debug options

Mario Charest wrote:
> Don't know what button you are talking about? 
> 
>> -----Original Message-----
>> From: Elena Laskavaia [mailto:community-noreply@qnx.com]
>> Sent: January-21-09 5:09 PM
>> To: general-ide
>> Subject: Re: Profiler strangeness
>>
>> On the other hand, I had button "disable automatic refresh" on which
>> prevent refresh (looks like lock).
>> When I unpress it - it starts refreshing.
>> Is yours enabled?
>>
>> _______________________________________________
>> General
>> http://community.qnx.com/sf/go/post20543
>>
> 
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post20544
> 
RE: Profiler strangeness  

> -----Original Message-----
> From: Elena Laskavaia [mailto:community-noreply@qnx.com]
> Sent: January-21-09 5:16 PM
> To: general-ide
> Subject: Re: Profiler strangeness
> 
> In Execution time view there is a button that looks like "lock" and
> tooltip says "Prevent auto-refresh" or "Scroll-lock".

Ah ok its not selected
> 
> The other problem may be that qconn does not have enough time slice to
> transfer the data and it times-out and give up on updates.

Machine is has 4 cores and all 4 cores are not doing much ( my test program is a for loop with sleep(1) in it...)

> You can enabled debug tracing (if you want to help to figure it out) by
> creating a file "options"

Ok will do.

Thanks a lot!

> ---
> com.qnx.tools.ide.profiler2.core/debug=false
> ---
> and running qde with extra option
> -debug options
> 
> Mario Charest wrote:
> > Don't know what button you are talking about?
> >
> >> -----Original Message-----
> >> From: Elena Laskavaia [mailto:community-noreply@qnx.com]
> >> Sent: January-21-09 5:09 PM
> >> To: general-ide
> >> Subject: Re: Profiler strangeness
> >>
> >> On the other hand, I had button "disable automatic refresh" on which
> >> prevent refresh (looks like lock).
> >> When I unpress it - it starts refreshing.
> >> Is yours enabled?
> >>
> >> _______________________________________________
> >> General
> >> http://community.qnx.com/sf/go/post20543
> >>
> >
> >
> > _______________________________________________
> > General
> > http://community.qnx.com/sf/go/post20544
> >
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post20545
> 
RE: Profiler strangeness  
> You can enabled debug tracing (if you want to help to figure it out) by
> creating a file "options"
> ---
> com.qnx.tools.ide.profiler2.core/debug=false
> ---

Please excuse my ignorance but I`m not exactly sure what you want me to do.  What does file "options" mean.  

> and running qde with extra option
> -debug options
> 
> Mario Charest wrote:
> > Don't know what button you are talking about?
> >
> >> -----Original Message-----
> >> From: Elena Laskavaia [mailto:community-noreply@qnx.com]
> >> Sent: January-21-09 5:09 PM
> >> To: general-ide
> >> Subject: Re: Profiler strangeness
> >>
> >> On the other hand, I had button "disable automatic refresh" on which
> >> prevent refresh (looks like lock).
> >> When I unpress it - it starts refreshing.
> >> Is yours enabled?
> >>
> >> _______________________________________________
> >> General
> >> http://community.qnx.com/sf/go/post20543
> >>
> >
> >
> > _______________________________________________
> > General
> > http://community.qnx.com/sf/go/post20544
> >
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post20545
> 
Re: Profiler strangeness  
File named "options". It would have 1 line with text below.
You can name it whatever you want just pass to -debug <file>.
Output should be in the eclipse log.

Mario Charest wrote:
>> You can enabled debug tracing (if you want to help to figure it out) by
>> creating a file "options"
>> ---
>> com.qnx.tools.ide.profiler2.core/debug=false
>> ---
> 
> Please excuse my ignorance but I`m not exactly sure what you want me to do.  What does file "options" mean.  
> 
>> and running qde with extra option
>> -debug options
>>
>> Mario Charest wrote:
>>> Don't know what button you are talking about?
>>>
>>>> -----Original Message-----
>>>> From: Elena Laskavaia [mailto:community-noreply@qnx.com]
>>>> Sent: January-21-09 5:09 PM
>>>> To: general-ide
>>>> Subject: Re: Profiler strangeness
>>>>
>>>> On the other hand, I had button "disable automatic refresh" on which
>>>> prevent refresh (looks like lock).
>>>> When I unpress it - it starts refreshing.
>>>> Is yours enabled?
>>>>
>>>> _______________________________________________
>>>> General
>>>> http://community.qnx.com/sf/go/post20543
>>>>
>>>
>>> _______________________________________________
>>> General
>>> http://community.qnx.com/sf/go/post20544
>>>
>> _______________________________________________
>> General
>> http://community.qnx.com/sf/go/post20545
>>
> 
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post20587
> 
RE: Profiler strangeness  

Very little in the log file, I can see -debug options.txt is there, so I did that part right. The file options.txt 
contains:

	com.qnx.tools.ide.profiler2.core/debug=false

I tried setting debug to true but no change. Funny how the IDE makes my 20 years of experience useless.  Feels like I 
have to learn everything from scratch, probably not a bad thing ;-)

Here is the log file:

!SESSION 2009-01-22 11:09:56.112 -----------------------------------------------
eclipse.buildId=I20081216
java.version=1.5.0_11
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_CA
Command-line arguments:  -os win32 -ws win32 -arch x86 -debug options.txt

!ENTRY org.eclipse.osgi 2 1 2009-01-22 11:10:00.562
!MESSAGE NLS missing message: ExportWizardPage_ErrorsDescription in: com.qnx.tools.ide.profiler2.ui.exportWizards.
messages

!ENTRY org.eclipse.osgi 2 1 2009-01-22 11:10:00.567
!MESSAGE NLS missing message: ExportWizardPage_EventsDescription in: com.qnx.tools.ide.profiler2.ui.exportWizards.
messages

!ENTRY org.eclipse.ui.workbench 2 0 2009-01-22 11:10:01.007
!MESSAGE A handler conflict occurred.  This may disable some commands.
!SUBENTRY 1 org.eclipse.ui.workbench 2 0 2009-01-22 11:10:01.007
!MESSAGE Conflict for 'AUTOGEN:::org.eclipse.ui.cheatsheets.actionSet/org.eclipse.ui.cheatsheets.actions.
CheatSheetHelpMenuAction':
HandlerActivation(commandId=AUTOGEN:::org.eclipse.ui.cheatsheets.actionSet/org.eclipse.ui.cheatsheets.actions.
CheatSheetHelpMenuAction,
	handler=ActionDelegateHandlerProxy(null,org.eclipse.ui.cheatsheets.CheatSheetExtensionFactory:helpMenuAction),
	expression=AndExpression(ActionSetExpression(org.eclipse.ui.cheatsheets.actionSet,org.eclipse.ui.internal.
WorkbenchWindow@4ca6b6),WorkbenchWindowExpression(org.eclipse.ui.internal.WorkbenchWindow@4ca6b6)),sourcePriority=16640)

HandlerActivation(commandId=AUTOGEN:::org.eclipse.ui.cheatsheets.actionSet/org.eclipse.ui.cheatsheets.actions.
CheatSheetHelpMenuAction,
	handler=ActionDelegateHandlerProxy(null,org.eclipse.ui.cheatsheets.CheatSheetExtensionFactory:helpMenuAction),
	expression=AndExpression(ActionSetExpression(org.eclipse.ui.cheatsheets.actionSet,org.eclipse.ui.internal.
WorkbenchWindow@4ca6b6),WorkbenchWindowExpression(org.eclipse.ui.internal.WorkbenchWindow@4ca6b6)),sourcePriority=16640)


> -----Original Message-----
> From: Elena Laskavaia [mailto:community-noreply@qnx.com]
> Sent: January-22-09 9:57 AM
> To: general-ide
> Subject: Re: Profiler strangeness
> 
> File named "options". It would have 1 line with text below.
> You can name it whatever you want just pass to -debug <file>.
> Output should be in the eclipse log.
> 

Re: Profiler strangeness  
Sorry I has to be "true" not "false".
Hmm if nothing in the log it should be on console then. Try to run eclipsec.exe instead of qde (which would not open 
second terminal and show console output).
When you run profiling it should print lots of stuff there...


Mario Charest wrote:
> 
> Very little in the log file, I can see -debug options.txt is there, so I did that part right. The file options.txt 
contains:
> 
> 	com.qnx.tools.ide.profiler2.core/debug=false
> 
> I tried setting debug to true but no change. Funny how the IDE makes my 20 years of experience useless.  Feels like I 
have to learn everything from scratch, probably not a bad thing ;-)
> 
> Here is the log file:
> 
> !SESSION 2009-01-22 11:09:56.112 -----------------------------------------------
> eclipse.buildId=I20081216
> java.version=1.5.0_11
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_CA
> Command-line arguments:  -os win32 -ws win32 -arch x86 -debug options.txt
> 
> !ENTRY org.eclipse.osgi 2 1 2009-01-22 11:10:00.562
> !MESSAGE NLS missing message: ExportWizardPage_ErrorsDescription in: com.qnx.tools.ide.profiler2.ui.exportWizards.
messages
> 
> !ENTRY org.eclipse.osgi 2 1 2009-01-22 11:10:00.567
> !MESSAGE NLS missing message: ExportWizardPage_EventsDescription in: com.qnx.tools.ide.profiler2.ui.exportWizards.
messages
> 
> !ENTRY org.eclipse.ui.workbench 2 0 2009-01-22 11:10:01.007
> !MESSAGE A handler conflict occurred.  This may disable some commands.
> !SUBENTRY 1 org.eclipse.ui.workbench 2 0 2009-01-22 11:10:01.007
> !MESSAGE Conflict for 'AUTOGEN:::org.eclipse.ui.cheatsheets.actionSet/org.eclipse.ui.cheatsheets.actions.
CheatSheetHelpMenuAction':
> HandlerActivation(commandId=AUTOGEN:::org.eclipse.ui.cheatsheets.actionSet/org.eclipse.ui.cheatsheets.actions.
CheatSheetHelpMenuAction,
> 	handler=ActionDelegateHandlerProxy(null,org.eclipse.ui.cheatsheets.CheatSheetExtensionFactory:helpMenuAction),
> 	expression=AndExpression(ActionSetExpression(org.eclipse.ui.cheatsheets.actionSet,org.eclipse.ui.internal.
WorkbenchWindow@4ca6b6),WorkbenchWindowExpression(org.eclipse.ui.internal.WorkbenchWindow@4ca6b6)),sourcePriority=16640)

> HandlerActivation(commandId=AUTOGEN:::org.eclipse.ui.cheatsheets.actionSet/org.eclipse.ui.cheatsheets.actions.
CheatSheetHelpMenuAction,
> 	handler=ActionDelegateHandlerProxy(null,org.eclipse.ui.cheatsheets.CheatSheetExtensionFactory:helpMenuAction),
> 	expression=AndExpression(ActionSetExpression(org.eclipse.ui.cheatsheets.actionSet,org.eclipse.ui.internal.
WorkbenchWindow@4ca6b6),WorkbenchWindowExpression(org.eclipse.ui.internal.WorkbenchWindow@4ca6b6)),sourcePriority=16640)

> 
>> -----Original Message-----
>> From: Elena Laskavaia [mailto:community-noreply@qnx.com]
>> Sent: January-22-09 9:57 AM
>> To: general-ide
>> Subject: Re: Profiler strangeness
>>
>> File named "options". It would have 1 line with text below.
>> You can name it whatever you want just pass to -debug <file>.
>> Output should be in the eclipse log.
>>
> 
> 
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post20628
> 
RE: Profiler strangeness  
First I tried eclipsec.exe with no option. At startup in the console I saw:

Failed to create property for: Session Persistent Storage

I started a profile session but nothing showed up.  I created a shortcut to eclipsec.exe and added the -debug <file>.  
Started eclipsec.exe more stuff came up, good. I can see a message about loading the debug file I created that contained
 " com.qnx.tools.ide.profiler2.core/debug=true". So far so good. Started a profile session, nothing showed up on the 
console. Bummer.

Too make sure I'm doing thing rights I added org.eclipse.update.core/debug=true to the debug options. When I when in the
 update manager I could see some debug print so my option file is working ok!!! I thought maybe the spec of what to 
debug is wrong.  I went berserk and options.txt became ugly.  Remember I have no idea what I'm doing but at least I'm 
trying to be creative.

Note that QNX_HOST is set to c:/qnx632/...  Will eclipse use the plugin from 6.4.0 or 6.3.2

com.qnx.tools.ide.profiler2.core/debug=true
com.qnx.tools.ide.profiler2.core_4.5.0/debug=true
com.qnx.tools.ide.profiler2.core_4/debug=true
com.qnx.tools.ide.profiler2.core_4.5.0.v200810092330/debug=true
com.qnx.tools.ide.profiler2.ui/debug=true
com.qnx.tools.ide.profiler.core/debug=true


That seems to do something, phew! 19:4:1 is when I started the profile session.

Start VM: -Dpath=%QNX_HOST%\usr\bin;%path%
-Xms512M
-Xmx768M
-XX:MaxPermSize=256m
-Djava.class.path=C:\eclipse\plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20080819.jar
-os win32
-ws win32
-arch x86
-showsplash
-launcher C:\eclipse\qde.exe
-name Qde
--launcher.library C:\eclipse\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731\eclipse_1115.
dll
-startup C:\eclipse\plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20080819.jar
-debug options.txt
-vm C:\eclipse\jre\bin\client\jvm.dll
-vmargs
-Dpath=%QNX_HOST%\usr\bin;%path%
-Xms512M
-Xmx768M
-XX:MaxPermSize=256m
-Djava.class.path=C:\eclipse\plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20080819.jar
Install location:
    file:/c:/eclipse/
Configuration file:
    file:/c:/eclipse/configuration/config.ini loaded
Configuration location:
    file:/C:/Users/mcharest.COMACT/momentics/4.6/configuration/
Configuration file:
    file:/C:/Users/mcharest.COMACT/momentics/4.6/configuration/config.ini not found or not read
Shared configuration location:
    file:/c:/eclipse/configuration/
Framework located:
    file:/c:/eclipse/plugins/org.eclipse.osgi_3.4.2.R34x_v20080826-1230.jar
Framework classpath:
    file:/c:/eclipse/plugins/org.eclipse.osgi_3.4.2.R34x_v20080826-1230.jar
Splash location:
    C:\Users\mcharest.COMACT\momentics\4.6\configuration\org.eclipse.equinox.launcher\com.qnx.tools.ide.momentics_4.6.0.
v200812041428\splash.bmp
Debug options:
    file:/C:/eclipse/options.txt loaded
Time to load bundles: 4
Starting application: 581
failed to create property for: Session Persistent Storage
<19:0:6> EVENT:  selection
<19:0:6> EVENT:  forget
<19:0:6> EVENT:  open
<19:0:6> EVENT:  selection
<19:0:6> EVENT:  forget
<19:0:6> EVENT:  open
<19:0:6> EVENT:  visible: true
<19:0:6> EVENT:  open
Application Started: 4940

<19:3:43> EVENT:  selection
<19:3:43> EVENT:  forget
<19:3:43> EVENT:  open
<19:3:43> start open job null
<19:3:43> EVENT:  selection
<19:3:43> EVENT:  forget
<19:3:43> EVENT:  open
<19:3:43> EVENT:  visible: true
<19:3:43> EVENT:  open
<19:3:43> end open job null
<19:3:43> start open job null
<19:3:43> end open job null
<19:3:43> start open job null
<19:3:43> end open job null

// THIS IS WHEN I STARTED THE PROFILE SESSION!

<19:4:1> EVENT:  conf (1) -> {root NO_CHANGE 0[conf (1) CHANGED 32768 PROP[]]}
<19:4:1> EVENT:  conf (1) -> {root NO_CHANGE 0[conf (1) CHANGED 32768...
View Full Message
Re: Profiler strangeness  
Thanks... Looks like updater works properly but you not getting any data... Is qconn blocked or something? I wish I can 
reproduce it...


Mario Charest wrote:
> First I tried eclipsec.exe with no option. At startup in the console I saw:
> 
> Failed to create property for: Session Persistent Storage
> 
> I started a profile session but nothing showed up.  I created a shortcut to eclipsec.exe and added the -debug <file>. 
 Started eclipsec.exe more stuff came up, good. I can see a message about loading the debug file I created that 
contained " com.qnx.tools.ide.profiler2.core/debug=true". So far so good. Started a profile session, nothing showed up 
on the console. Bummer.
> 
> Too make sure I'm doing thing rights I added org.eclipse.update.core/debug=true to the debug options. When I when in 
the update manager I could see some debug print so my option file is working ok!!! I thought maybe the spec of what to 
debug is wrong.  I went berserk and options.txt became ugly.  Remember I have no idea what I'm doing but at least I'm 
trying to be creative.
> 
> Note that QNX_HOST is set to c:/qnx632/...  Will eclipse use the plugin from 6.4.0 or 6.3.2
> 
> com.qnx.tools.ide.profiler2.core/debug=true
> com.qnx.tools.ide.profiler2.core_4.5.0/debug=true
> com.qnx.tools.ide.profiler2.core_4/debug=true
> com.qnx.tools.ide.profiler2.core_4.5.0.v200810092330/debug=true
> com.qnx.tools.ide.profiler2.ui/debug=true
> com.qnx.tools.ide.profiler.core/debug=true
> 
> 
> That seems to do something, phew! 19:4:1 is when I started the profile session.
> 
> Start VM: -Dpath=%QNX_HOST%\usr\bin;%path%
> -Xms512M
> -Xmx768M
> -XX:MaxPermSize=256m
> -Djava.class.path=C:\eclipse\plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20080819.jar
> -os win32
> -ws win32
> -arch x86
> -showsplash
> -launcher C:\eclipse\qde.exe
> -name Qde
> --launcher.library C:\eclipse\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731\eclipse_1115
.dll
> -startup C:\eclipse\plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20080819.jar
> -debug options.txt
> -vm C:\eclipse\jre\bin\client\jvm.dll
> -vmargs
> -Dpath=%QNX_HOST%\usr\bin;%path%
> -Xms512M
> -Xmx768M
> -XX:MaxPermSize=256m
> -Djava.class.path=C:\eclipse\plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20080819.jar
> Install location:
>     file:/c:/eclipse/
> Configuration file:
>     file:/c:/eclipse/configuration/config.ini loaded
> Configuration location:
>     file:/C:/Users/mcharest.COMACT/momentics/4.6/configuration/
> Configuration file:
>     file:/C:/Users/mcharest.COMACT/momentics/4.6/configuration/config.ini not found or not read
> Shared configuration location:
>     file:/c:/eclipse/configuration/
> Framework located:
>     file:/c:/eclipse/plugins/org.eclipse.osgi_3.4.2.R34x_v20080826-1230.jar
> Framework classpath:
>     file:/c:/eclipse/plugins/org.eclipse.osgi_3.4.2.R34x_v20080826-1230.jar
> Splash location:
>     C:\Users\mcharest.COMACT\momentics\4.6\configuration\org.eclipse.equinox.launcher\com.qnx.tools.ide.momentics_4.6.
0.v200812041428\splash.bmp
> Debug options:
>     file:/C:/eclipse/options.txt loaded
> Time to load bundles: 4
> Starting application: 581
> failed to create property for: Session Persistent Storage
> <19:0:6> EVENT:  selection
> <19:0:6> EVENT:  forget
> <19:0:6> EVENT:  open
> <19:0:6> EVENT:  selection
> <19:0:6> EVENT:  forget
> <19:0:6> EVENT:  open
> <19:0:6> EVENT:  visible: true
> <19:0:6> EVENT:  open
> Application Started: 4940
> 
> <19:3:43> EVENT:  selection
> <19:3:43> EVENT:  forget
> <19:3:43> EVENT:  open
> <19:3:43> start open job null
> <19:3:43>...
View Full Message
RE: Profiler strangeness  

> -----Original Message-----
> From: Elena Laskavaia [mailto:community-noreply@qnx.com]
> Sent: January-23-09 10:08 AM
> To: general-ide
> Subject: Re: Profiler strangeness
> 
> Thanks... Looks like updater works properly but you not getting any
> data... Is qconn blocked or something? I wish I can reproduce it...


Aaaaaaaaaaaaaaaaaahhhhhhhhhhhhhhhhhhhhhh, got it.  In the profiler configuration I had setup an Environment variable 
that I forgot about: QPROF_FILE=/tmp/prof.trace.  On the target and in the Tools/Application Profiler I used /tmp/prof.
ptrace.  I have no idea why the profiler was influenced by this environment variable but it is. It's attaching to the 
process not launching it.

Thanks for your time.  For conclusion I'm going to raise my hand for some better error reporting.  I'd welcome a  "can't
 find profile file <file> " message.

Thanks again

> 
> 
> Mario Charest wrote:
> > First I tried eclipsec.exe with no option. At startup in the console
> I saw:
> >
> > Failed to create property for: Session Persistent Storage
> >
> > I started a profile session but nothing showed up.  I created a
> shortcut to eclipsec.exe and added the -debug <file>.  Started
> eclipsec.exe more stuff came up, good. I can see a message about
> loading the debug file I created that contained "
> com.qnx.tools.ide.profiler2.core/debug=true". So far so good. Started a
> profile session, nothing showed up on the console. Bummer.
> >
> > Too make sure I'm doing thing rights I added
> org.eclipse.update.core/debug=true to the debug options. When I when in
> the update manager I could see some debug print so my option file is
> working ok!!! I thought maybe the spec of what to debug is wrong.  I
> went berserk and options.txt became ugly.  Remember I have no idea what
> I'm doing but at least I'm trying to be creative.
> >
> > Note that QNX_HOST is set to c:/qnx632/...  Will eclipse use the
> plugin from 6.4.0 or 6.3.2
> >
> > com.qnx.tools.ide.profiler2.core/debug=true
> > com.qnx.tools.ide.profiler2.core_4.5.0/debug=true
> > com.qnx.tools.ide.profiler2.core_4/debug=true
> > com.qnx.tools.ide.profiler2.core_4.5.0.v200810092330/debug=true
> > com.qnx.tools.ide.profiler2.ui/debug=true
> > com.qnx.tools.ide.profiler.core/debug=true
> >
> >
> > That seems to do something, phew! 19:4:1 is when I started the
> profile session.
> >
> > Start VM: -Dpath=%QNX_HOST%\usr\bin;%path%
> > -Xms512M
> > -Xmx768M
> > -XX:MaxPermSize=256m
> > -
> Djava.class.path=C:\eclipse\plugins\org.eclipse.equinox.launcher_1.0.10
> 1.R34x_v20080819.jar
> > -os win32
> > -ws win32
> > -arch x86
> > -showsplash
> > -launcher C:\eclipse\qde.exe
> > -name Qde
> > --launcher.library
> C:\eclipse\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.101
> .R34x_v20080731\eclipse_1115.dll
> > -startup
> C:\eclipse\plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20080819.
> jar
> > -debug options.txt
> > -vm C:\eclipse\jre\bin\client\jvm.dll
> > -vmargs
> > -Dpath=%QNX_HOST%\usr\bin;%path%
> > -Xms512M
> > -Xmx768M
> > -XX:MaxPermSize=256m
> > -
> Djava.class.path=C:\eclipse\plugins\org.eclipse.equinox.launcher_1.0.10
> 1.R34x_v20080819.jar
> > Install location:
> >     file:/c:/eclipse/
> > Configuration file:
> >     file:/c:/eclipse/configuration/config.ini loaded
> > Configuration location:
> >     file:/C:/Users/mcharest.COMACT/momentics/4.6/configuration/
> > Configuration file:
> >
> file:/C:/Users/mcharest.COMACT/momentics/4.6/configuration/config.ini
> not found or not...
View Full Message
Re: Profiler strangeness  
I am glad you resolved that. I am not sure I can add an error message because "upload while running" mode waits until 
file is created on the target indefinitely
(maybe I can time-out this, I will open pr). Env vars should probably not be there, it is used by host site to determine
 some options that was passed to the program,
but better way would be to ask the program itself on the target side...
RE: Profiler strangeness  

> -----Original Message-----
> From: Elena Laskavaia [mailto:community-noreply@qnx.com]
> Sent: January-23-09 1:34 PM
> To: general-ide
> Subject: Re: Profiler strangeness
> 
> I am glad you resolved that. I am not sure I can add an error message
> because "upload while running" mode waits until file is created on the
> target indefinitely
> (maybe I can time-out this, I will open pr).

If you attach to a process shouldn`t the file be already there?  Although I guess it could have be started with on -h, 
so that wouldn't work.

Thinking out loud:

- Have the file name displayed in the properties view, so at least we'd know what file it's trying to get.
- Having some sort of status in the Properties as to what it's doing, waiting for file <filename>..., uploading, etc.  -
 The profiler could read the value of QPROF_FILE from the process itself, that way no possibility of error.  Could even 
tell if the variable isn't set properly,  check if the path is valid etc.

> Env vars should probably
> not be there, it is used by host site to determine some options that
> was passed to the program,
> but better way would be to ask the program itself on the target side...

You outthought me on that one, lol!

> 
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post20738
> 
Re: Profiler strangeness  
PR#64877 Application Profiler - improve settings sharing between tool and remote process when attaching

Description:   	 Opened: 2009-01-23 13:59

When attaching to running session it is important that attaching configuration
have same profiler setting as one that running on target. Currently it is
achieved by manually insuring that same file and method are used.
The better way would be to read environment variables used by remote process,
and extract settings from there, which leaves no room for mistake.

Also diagnostics can be improved by showing setting that are used by the tool
(such as remote file name) in the profiler view or in the properties view.
RE: Profiler strangeness  
And again thanks for listening!

> -----Original Message-----
> From: Elena Laskavaia [mailto:community-noreply@qnx.com]
> Sent: January-23-09 2:01 PM
> To: general-ide
> Subject: Re: Profiler strangeness
> 
> PR#64877 Application Profiler - improve settings sharing between tool
> and remote process when attaching
> 
> Description:   	 Opened: 2009-01-23 13:59
> 
> When attaching to running session it is important that attaching
> configuration
> have same profiler setting as one that running on target. Currently it
> is
> achieved by manually insuring that same file and method are used.
> The better way would be to read environment variables used by remote
> process,
> and extract settings from there, which leaves no room for mistake.
> 
> Also diagnostics can be improved by showing setting that are used by
> the tool
> (such as remote file name) in the profiler view or in the properties
> view.
> 
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post20747
>