This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: segfault

From: John Fine <johnsfine at verizon dot net>
To: Leonardo Santagostini <lsantagostini at gmail dot com>
Cc: "John (Eljay) Love-Jensen" <eljay at adobe dot com>, gcc-help at gcc dot gnu dot org
Date: Tue, 09 Dec 2008 12:01:19 -0500
Subject: Re: segfault
References: <9ab7eeeb0812090635ndc60ecfl5fe2e3bcd25e20ef@mail.gmail.com> <C563E3CB.36815%eljay@adobe.com> <9ab7eeeb0812090714s2aaa04e0m80e4ea9c4c1824b@mail.gmail.com>

For most segfaults, I find it easier to use ulimit to make coredumps temporarily unlimited, then rerun the original program to fail again, but now that will generate a core file.

Then open the image and core file together in gdb. You don't need much gdb knowledge (more than I remember right now, but still not much) to get a backtrace (call stack from the failure point up through main). Usually that is enough to identify the exact bug.

If it isn't, then you build with more debug info and use gdb in more challenging ways.

Leonardo Santagostini wrote:

Thanks for the answers, i will do the following things:
1) To read and learn how to use the GDB :D !!
2) Compile -g3 RGPVISAServer
3) Attach gdb to a runnig RGPVISAServer process to see what is doing wrong.
Well, after finish i will publish my error, thanks for support me !!!!

Follow-Ups:
- Re: segfault
  - From: Leonardo Santagostini

References:
- Re: segfault
  - From: Leonardo Santagostini

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]