Programming

Stack overflow, I. declaration size of your stack is small, may be you should increase it.
Coredump , sometimes it appears when you try to compile and you had already made *.o etc which we could say has formed a file called core .Sometimes you have to delete them and then compile afresh.

Regards
Gerald.

hi!

could u plz tell me how do i increase the stack size?

Regards
SHAIK

I think the first thing you want to do is to
examine the core file using a debugger. The
debugger you use will depend on the compiler
tools you are using. For instance, if you are
using gcc/g++ you can debug using gdb. Using
gdb, you can load the program executable
along with the core file and run the "bt"
(backtrace) command to find exactly where the
program is failing. It would be better to have
the program compiled using the "-g" (for gcc)
option so that a symbol table is created so you
can follow the program execution in a very
detailed manner.

If you are not using the GNU compiler/debugger
then you'll have to find out what debugger
you have on your system (i.e. ladebug, dbx, sdb,
adb, etc...)

On increasing the stack size, you will have to
check your compiler documentation as this is
very compiler dependent.

thanks.

Shaik

Hi rwb1959,

Can you please suggest any documentation explaining how to use these various debuggers. I am having a wild goose-chase trying to find the source of a memory fault that happens on our customers, but I cannot imitate it on my own development machine. I now have a core dump, but I need to know what to do with it.

Thanks.

Hi ebh,

If you can tell me what compiler suite you are
using, I can be more specific however, the
following link is for GDB...
http://sources.redhat.com/gdb/onlinedocs/gdb_toc.html

...It would be best to actually debug it on the
customer machine if possible but I understand
that that is not always doable. You will also
need the actual executable that they are running
as well unless you can build what they have.
I assume that your development
environment is at least the same (i.e. same
type of UNIX on same type of hardware - RISC, etc)
Assuming this was built for a production
environment, I would expect that it was not
compiled with symbol tables (i.e. "-g" option).
It may help to build them a new version with
this option on and install it on their system
and duplicate the core dump then use the new
core with the new executable. The information
you get will be much more "readable" and will
"map" to your source code much more easily.

Hi rwb1959,

First of all, thanks for your quieck reply.

We are running sco, and using the compiler that comes along with it. I recomplied the program with the -g flag, but we have already updated the effected program, so I will now need to wait till it happens again.

So, the next time the customer gets a memory fault, I will copy the core dump to my machine and I will try to debug. The question is which debugger to use, since I don't think gdb will work if we don't use gcc. I have heard about adb and dbx, but I don;t know how to use either of them.