wprof generating a SIGSEGV

QNX Newsgroups (Archives) qdn.public.qnx4.devtools
1

I am trying to profile an executable to identify any performance issues in
the code execution. I can successfully capture the data with “sample” and
get a file MyExecutable.smp. I then try to run “wprof MyExecutable.smp”.
wprof then generated a SIGSEGV and terminates. Any suggestions??? Has
anyone else seen this???

I can successfully perform a “sample” and “wprof” on executables such as
‘ls’, ‘cat’, etc. But no luck on any executable I created… Is there a
compiler switch I need to be setting???

Any help is greatly appreciated…
Thanks in advance,

Andy

2

I had similar problems profiling when I used Full debugging info (-d2) and
Dwarf format. I changed the debug options to just Line number information
(-d1) and Compiler default (WATCOM) format and voila I can profile.

Hope this helps,

Richard

“Andrew Kissel” <amk@availtec.com> wrote in message
news:9o7jbj$goc$1@inn.qnx.com…

I am trying to profile an executable to identify any performance issues in
the code execution. I can successfully capture the data with “sample” and
get a file MyExecutable.smp. I then try to run “wprof MyExecutable.smp”.
wprof then generated a SIGSEGV and terminates. Any suggestions??? Has
anyone else seen this???

I can successfully perform a “sample” and “wprof” on executables such as
‘ls’, ‘cat’, etc. But no luck on any executable I created… Is there a
compiler switch I need to be setting???

Any help is greatly appreciated…
Thanks in advance,

Andy

3

Richard,
Thanks for the info, that did it!!!

Andy


“Brown, Richard” <brownr@aecl.ca> wrote in message
news:9o7jnq$h2s$1@inn.qnx.com…

I had similar problems profiling when I used Full debugging info (-d2) and
Dwarf format. I changed the debug options to just Line number information
(-d1) and Compiler default (WATCOM) format and voila I can profile.

Hope this helps,

Richard

“Andrew Kissel” <> amk@availtec.com> > wrote in message
news:9o7jbj$goc$> 1@inn.qnx.com> …
I am trying to profile an executable to identify any performance issues
in
the code execution. I can successfully capture the data with “sample”
and
get a file MyExecutable.smp. I then try to run “wprof MyExecutable.smp”.
wprof then generated a SIGSEGV and terminates. Any suggestions??? Has
anyone else seen this???

I can successfully perform a “sample” and “wprof” on executables such as
‘ls’, ‘cat’, etc. But no luck on any executable I created… Is there a
compiler switch I need to be setting???

Any help is greatly appreciated…
Thanks in advance,

Andy
\