I too have had similar problems. they are usually because of stack corruption/stack overflow. eg. writing off the bounds of a local char buffer.
could u pls post the code. --- In [email protected], Kiran Divakaran <[EMAIL PROTECTED]> wrote: > > Hi All, > > I have a strange problem . One of the functions in the application we use is dumping core. > > Once we put fprintf inside the function and traced through the file , the core stops appearing . So the only change that was done to the file was to > > put fprintfs inside it that to debug it and trace through the last function which was appearing on the core stack. > > Apparently this is preventing the core from being dumped on SunOS. > > Also there are strange things like if the fprintf is commented / added at particular points in the function then the core issue reappears. > > Is it got to do with the stack being in a inconsistent state and calling a fprintf restores it unloads it in some way and things get back to working. > > The stack should behave the way it is supposed to as a part of the Operating system and would be the last thing to suspect it. > > But there have been issues like in the past where HP/SUN had genuine bugs in their OS and later provided patches when raised with them. > > Is that the situation here or do we need to probe something on our application front. > > Please let know your inputs on the same or rather explain this issue technically as to what might be happening ? > > > Regards, > Kiran > > > > > **************** CAUTION - Disclaimer ***************** > This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely > for the use of the addressee(s). If you are not the intended recipient, please > notify the sender by e-mail and delete the original message. Further, you are not > to copy, disclose, or distribute this e-mail or its contents to any other person and > any such actions are unlawful. This e-mail may contain viruses. Infosys has taken > every reasonable precaution to minimize this risk, but is not liable for any damage > you may sustain as a result of any virus in this e-mail. You should carry out your > own virus checks before opening the e-mail or attachment. Infosys reserves the > right to monitor and review the content of all messages sent to or from this e-mail > address. Messages sent to or from this e-mail address may be stored on the > Infosys e-mail system. > ***INFOSYS******** End of Disclaimer ********INFOSYS*** > > > [Non-text portions of this message have been removed] >
