[techtalk] A SIGSEGV problem

[Deepa Karnad]

Hi everybody.
It is sometime now that I asked for help regarding a particular SIGSEGV
problem. The problem was solved today. The real problem was elsewhere and
SIGSEGV must have cropped up as a side-effect.

I had initially worked on the c/c++ pgm in Windows. Had a few data files
that was used in that pgm. Then I had ported the entire pgm AND the data
files to linux using a floppy. The problem lay in the data files themselves
cuz they were not being recognised by linux. Today I created fresh data
files in linux itself. The software program then worked like magic.

While compiling, the memory address used while reading those erroneous files
must have caused the SIGSEGV. Thanks for all the help by everybody who
volunteered.
Deepa
-----Original Message-----


>> A  g++ program is encountering problems during execution. There are no
>> error messages as it gets linked and compiled. The executable file
>> does not run though. These are the error messages observed: 'Program
>> received a signal SIGSEGV, segmentation fault' OR 'Segmentation fault
>> (core dumped)'
>>  I understand this could be a memory access problem but do not know
>> how to set the problem right.
>
>BAD memory (again).
>
>gcc segfaulting is a classic symptom.
>
> Jeff
>
>
>
>
>_______________________________________________
>techtalk mailing list
>techtalk at linuxchix.org
>http://www.linux.org.uk/mailman/listinfo/techtalk
>