'Memory fault(coredump)' Error message

[Anthony Wcislo]

I get this error from running a script that executes a command over and extensive amount of files. What causes this error message? How do I prevent this error from occurring?

[Sridhar Bhaskarla]

Anthony,

When you get the core file, do a
file core and see what output you are getting.

Depending on the error, you need to decide whehter you want to tune maxdsiz or maxssiz.

-Sri

[A. Clay Stephenson]

This simply means that the command is attempting an operation outside the bounds of normal memory. One example would be if an array were declared with 100 elements so that indices 0 - 99 are valid. The program might attempt to access element -3 or 451 and generate just this error.

One thing that does occur to me since you say this command is executed over many files is that the program is attempting to copy the argument list into an array that is too small. Does is crash when fed only a few filenames?

The other thing that can cause this is corrupt files. You really have to give us more to go on than this.

[Anthony Wcislo]

I did the command 'strings core|head -100|more' to look at the core file that was dumped. I attached it in a text file.

[A. Clay Stephenson]

Okay Anthony:

Time to call Baan Support and wait for their usual 2 or 3 day response.

[Sridhar Bhaskarla]

Anthony,

YOu can't get any information from strings. If you really want to debug the core file , we need to use xdb but that's too complicated.

What does your "file core" say?

-Sri

[Anthony Wcislo]

Yeah...I've had this case submitted to Baan for almost 3 weeks. I have better luck figuring it out myself. How can I read the core file? The only way I know to look at the core file is with the 'strings' command.

[T G Manikandan]

Hello,
#file core
what is the result.
for ex. the result gives a 'telnetd' as source
YOu can use gdb for examining your core file.
#/opt/langtools/bin/gdb telnetd core
gdb>where
You can start your debugging here.

[Anthony Wcislo]

I did the command '#file core' as told and the output was:
core: core file from 'tbase6.1' - received SIGSEGV
What does this mean and what do I need to do next?

[A. Clay Stephenson]

Hi again:

It's the same answer as before. The Baan executable is attempting an out of bounds memory operation - like exceeeding the boundaries of an array or attempting to write to a NULL address. This is NOT an OS issue but a programming/data error. The answer is to call Baan.

[T G Manikandan]

Hello,
#file core
#gdb 'tbase6.1' core
.....
gdb>where


....