This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: segfault
- From: "Leonardo Santagostini" <lsantagostini at gmail dot com>
- To: "John Fine" <johnsfine at verizon dot net>
- Cc: "John (Eljay) Love-Jensen" <eljay at adobe dot com>, gcc-help at gcc dot gnu dot org
- Date: Tue, 9 Dec 2008 17:07:11 -0200
- Subject: Re: segfault
- References: <9ab7eeeb0812090635ndc60ecfl5fe2e3bcd25e20ef@mail.gmail.com> <C563E3CB.36815%eljay@adobe.com> <9ab7eeeb0812090714s2aaa04e0m80e4ea9c4c1824b@mail.gmail.com> <493EA45F.4080200@verizon.net>
Hello Folks !!!
I have my mind broken in pieces, but i must assume i dont have enough skill.
Sorry for bother you.
Sincerelly
Leonardo
If someone wants to help me i will really appreciate
2008/12/9 John Fine <johnsfine@verizon.net>:
> 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 !!!!
>>
>>
>
>
--
Saludos.-
Leonardo Santagostini