Re: core dump using Pro*C on CONNECT

Originally posted by Pete Finnigan
> Hi thumor,
>
> OK, what I would do next is use the truss command to trace what is
> happening. (if you are on Unix, if linux i think its strace or ptrace,
> windows has an strace - but it is not very good - on windows
> you can use
> the free tools from sysinternals.com instead to see what is happening)
>
> Enable output so that you get calls to user libraries and not just the
> kernel. Using truss or equivalent you should get some clue as
> to what is
> happening. You will see which shared libraries are being opened and so
> on.
>
> A sample command that saves output and traces children, shows
> environment and traces library calls would be for instance to trace
> sqlplus:
>
> truss -faed -v -u '*' -o./pete.out sqlplus
>
> hth
>
> kind regards
>
> Pete
> --
> Pete Finnigan
> email:pete_at_petefinnigan.com
> Web site:
> http://www.petefinnigan.com/http://www.petefinnigan.com
> - Oracle security audit specialists
> Book:Oracle security step-by-step Guide - see
> http://store.sans.org/http://store.sans.org for details.
>

I am running on HP-UX 10.2
do not have truss. Any other tool that can help me here?

--
Posted via http://dbforums.com