T.R | Title | User | Personal Name | Date | Lines |
---|
299.1 | profiling an application built under ODE? | SMURF::FILTER | Automatic Posting Software - mail to flume::puck | Tue Sep 07 1993 11:05 | 27 |
| Date Of Receipt: 3-SEP-1993 16:38:05.40
From: ABYSS::swell::swr
To: abyss::odehelp
CC: swell::pav, swell::swr
Subj: profiling an application built under ODE?
Hi,
I'm trying to profile an application that I built under ODE. When I pix-ify it,
after building it, the pix-ified version core dumps upon execution. I tried
turning on the -p flag in the makefile, but when I run the resultant executable,
I don't get a "mon.out" file. The executable works fine, but doesn't produce
any profiling data.
I tried putting the "-p" in the CFLAGS, which compiles OK, but I get the above
results. When I put the "-p" in the LDFLAGS, I get the following error:
cc: Error: -p0 or -p1 must precede any -B flags
Can someone tell me the correct method for profiling an OSF command/utility
built under ODE?
Thanks very much,
Scott
|
299.2 | Re: profiling an application built under ODE? | SMURF::FILTER | Automatic Posting Software - mail to flume::puck | Tue Sep 07 1993 11:06 | 19 |
| Date Of Receipt: 3-SEP-1993 16:46:55.97
From: ABYSS::rust::ode
To: swell::swr
CC: abyss::odehelp
Subj: Re: profiling an application built under ODE?
hi scott,
i tried using CFLAGS=-p on a build.
cd to the obj directory where it created the .o and
image. in this directory i can run
pixie imagename
and it comes back with imagename.Addrs and imagename.pixie
is this close to what you're trying to do?
jo
|
299.3 | profiling an application built under ODE? | SMURF::FILTER | Automatic Posting Software - mail to flume::puck | Tue Sep 07 1993 11:08 | 64 |
| Date Of Receipt: 3-SEP-1993 17:03:48.74
From: WASTED::jmf "Joshua M. Friedman ULTRIX SDE 03-Sep-1993 1705"
To: buildhelp@wasted:zko.dec
CC:
Subj: profiling an application built under ODE?
buildhelp's the more appropriate alias for this... thanks.
------- Forwarded Message
Return-Path: [email protected]
Delivery-Date: Wed, 01 Sep 93 18:33:19 +28716
Return-Path: [email protected]
Received: by flambe.zk3.dec.com; id AA19724; Wed, 1 Sep 1993 18:33:16 -0400
Received: by wasted.zk3.dec.com; id AA05516; Wed, 1 Sep 1993 18:32:32 -0400
Received: by swell.unx.dec.com (5.65/MS-070792);
id AA05639; Wed, 1 Sep 1993 18:34:39 -0400
Message-Id: <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: profiling an application built under ODE?
Date: Wed, 01 Sep 93 18:34:38 -0400
From: [email protected]
X-Mts: smtp
Sorry for duplicates you'll get later, abyss isn't taking mail right now and I
need to get help on this. - thanks
- ------- Forwarded Message
From: swr
To: abyss::odehelp
Cc: pav, swr
Hi,
I'm trying to profile an application that I built under ODE. When I pix-ify it,
after building it, the pix-ified version core dumps upon execution. I tried
turning on the -p flag in the makefile, but when I run the resultant executable,
I don't get a "mon.out" file. The executable works fine, but doesn't produce
any profiling data.
I tried putting the "-p" in the CFLAGS, which compiles OK, but I get the above
results. When I put the "-p" in the LDFLAGS, I get the following error:
cc: Error: -p0 or -p1 must precede any -B flags
Can someone tell me the correct method for profiling an OSF command/utility
built under ODE?
Thanks very much,
Scott
- ------- End of Forwarded Message
------- End of Forwarded Message
|
299.4 | Re: profiling an application built under ODE? | SMURF::FILTER | Automatic Posting Software - mail to flume::puck | Tue Sep 07 1993 11:09 | 33 |
| Date Of Receipt: 3-SEP-1993 17:05:49.71
From: WASTED::"[email protected]" "03-Sep-1993 1708"
To: unxa::rust::ode
CC: [email protected], [email protected]
Subj: Re: profiling an application built under ODE?
Hi Jo,
>> i tried using CFLAGS=-p on a build.
Did it work for you?
I finally took my files and built the executable in the standard "user"
compilation environment on a Sterling BL5 system and added the -p flag there.
When I run this binary, I get the "mon.out" file as expected. This work-around
is fine for me.
>> cd to the obj directory where it created the .o and
>> image. in this directory i can run
>> pixie imagename
>> and it comes back with imagename.Addrs and imagename.pixie
This is basically what I did. However, I guess there are some problems with
pixie as my imagename.pixie file simply core dumps upon execution. I've
used it successfully in the past with other programs, though. (on ULTRIX and
OSF)
Thanks,
Scott
|