Brett Humphreys (bh253395@oak.cats.ohiou.edu)
Fri, 11 Jun 1999 15:10:59 -0400 (EDT)
I think it is gdb a.out core
where a.out is the compiled application that core dumped and core is the
core dump image that was spit out..
-brett
On Fri, 11 Jun 1999, Reid Ellis wrote:
> Evan wrote:
> >"segmentation fault (core dumped)"
> >
> >what does this mean (sounds bad ;).
>
> At 11:08 1999-06-11 -0400, JP Rosevear wrote:
> >Means there was a good 'ol memory access problem, many times caused by
> >dereferencing a null pointer. The kernel will then dump the core (the
> >processes' memory image), a hold over from the Un*x when it was possible
> >to look at the core and determine what went wrong - these days 10MB is a
> >fair bit more to look at than the 4k of yore.
>
> Actually, you can see what happened by doing something like "gdb core"
> [you can use your favorite debugger in place of 'gdb']. This is especially
> useful if the binary had symbols compiled in. Then you can examine which
> function it crashed in, what the values of all the variables were and
> usually figure out what went wrong. Most often saying something like "now
> how did THAT get to be NULL?".
>
> Reid
>
>
>
This archive was generated by hypermail 2.0b3 on Wed Jun 30 1999 - 11:30:09 MDT