J
J. D. Leach
I am not sure whether this would be considered off topic or not, but here
goes.....don't flame me too bad.
Running GNU GCC 4.0.1 and GDB 6.3. Was checking my compiler and debugger
output prior to doing some coding in C when I discovered that GDB doesn't
recognize the format of core dumps when I inject a segmentation fault. Was
able to to set ulimit and get the dump OK, but when I tried to gather the
error info by typing the following command: gdb ./crash_and_burn.c core, I
get an error stating that the core file is in an unrecognized format.
Come from a VB6 environment and am trying to learn C using the CLI and basic
tools and functions. I seem to understand the material a little better when
typing in the commands, and using a procedural technique, versus point and
click and objects (must be from when I worked with mainframes with the
military during the 70's).
--
J. D. Leach
Columbus, Indiana USA
Linux/Open Source Computer using:
Mandriva Linux release 2006.0 (Community) for i586 kernel 2.6.12-12mdk
goes.....don't flame me too bad.
Running GNU GCC 4.0.1 and GDB 6.3. Was checking my compiler and debugger
output prior to doing some coding in C when I discovered that GDB doesn't
recognize the format of core dumps when I inject a segmentation fault. Was
able to to set ulimit and get the dump OK, but when I tried to gather the
error info by typing the following command: gdb ./crash_and_burn.c core, I
get an error stating that the core file is in an unrecognized format.
Come from a VB6 environment and am trying to learn C using the CLI and basic
tools and functions. I seem to understand the material a little better when
typing in the commands, and using a procedural technique, versus point and
click and objects (must be from when I worked with mainframes with the
military during the 70's).
--
J. D. Leach
Columbus, Indiana USA
Linux/Open Source Computer using:
Mandriva Linux release 2006.0 (Community) for i586 kernel 2.6.12-12mdk