core format not recognized

Hi,

after running an application and getting an segmentation 
fault, I want to figure what part of the code is
responsible
for that. For this purpose I use GNU gdb 6.4.90-debian. I
run:
"gdb EXECUTABLE core" and get the error message:

core" is not a core dump: File format not recognized

(code is compiled with gcc 3.4.6 and -g)

So, debugging is not possible. Any ideas what might be
wrong?

Regards,
Chris
_______________________________________________
help-gnu-utils mailing list
help-gnu-utilsgnu.org

http://lists.gnu.org/mailman/listinfo/help-gnu-utils

No clue without examining your core file.

However, if your error is reproducible, you can still debug.
 Just run 
it under gdb.  When it fails, you'll be at a place suitable
for 
debugging just as though you were debugging with a core
file.

--rich

Christian Christmann wrote:
> Hi,
>
> after running an application and getting an
segmentation 
> fault, I want to figure what part of the code is
responsible
> for that. For this purpose I use GNU gdb 6.4.90-debian.
I run:
> "gdb EXECUTABLE core" and get the error
message:
>
> core" is not a core dump: File format not
recognized
>
> (code is compiled with gcc 3.4.6 and -g)
>
> So, debugging is not possible. Any ideas what might be
wrong?
>
> Regards,
> Chris
> _______________________________________________
> help-gnu-utils mailing list
> help-gnu-utilsgnu.org
> 
http://lists.gnu.org/mailman/listinfo/help-gnu-utils
>   


_______________________________________________
help-gnu-utils mailing list
help-gnu-utilsgnu.org

http://lists.gnu.org/mailman/listinfo/help-gnu-utils

Christian Christmann wrote:


> after running an application and getting an
segmentation 
> fault, I want to figure what part of the code is
responsible
> for that. For this purpose I use GNU gdb 6.4.90-debian.
I run:
> "gdb EXECUTABLE core" and get the error
message:

> core" is not a core dump: File format not
recognized

file core

should tell you that it is an appropriate core file, also

ls -l core

Note that many systems now write core files named after the
process id, and you may have an old core file from a
different system.

-- glen