Re: Forms 3 Problem - Please Help

From: P Seely <Peter.Seely_at_gov.nb.ca>
Date: Tue, 13 Jul 1999 17:14:55 GMT
Message-ID: <378b73fe.1573032_at_allnews.nbnet.nb.ca>


The user running the process owns the runform being executed. It's being initiated from that user's home directory, so I don't believe it could be a permissions issue.

It's not often I find myself wishing for a process to dump core. :)

We're on RS/6000 AIX 4.2.1.

Thanks
Peter

On Tue, 13 Jul 1999 16:46:00 +0100, "Karl E. Jørgensen" <abuse_at_nospam.com> wrote:

>If you don't have write permission to the current directory, no core file
>will be produced. I guess that's why there isn't a core file - I assume that
>your user exit doesn't call exit() :-)
>
>If you have the source for the user exit, then you should be able to make
>better use of the core file once you get it:
>1) Compile your runform with the option to include debugging information (as
>far as I remember that the -g option, but better check yourself)
>2) copy the newly generated runform to the server where the problem appears
>3) run it and produce a core file. If it does, expect a delay of a couple of
>seconds as core files from SQL*Forms can be rather sizeable.
>4) examine the core file - hopefully you will be able to produce a stack
>trace, which should help you pinpoint the problem.
>
>What platform are you using? Different platforms have different ways of
>examining core files - look for commands like xdb, dbx etc...
>
>Hope this helps
>
>
>--
>Karl E. Jorgensen
Received on Tue Jul 13 1999 - 19:14:55 CEST

Original text of this message