Debugging Gcc

Debugging Gcc

[Hari]

Hi,
 I am an undergraduate student at IIT Bombay working on the control flow
of GCC while compiling c code.I am intrested in tracing the path of gcc
during compilation.I don't see any good material on this topic anywhere.
 One approach is to  put break points in all of (176) c files 
in gcc directory and check the flow but that seems to be very time
consuming . Is there is anyother way out???

--Hari
 

Re: Debugging Gcc

[Ian Lance Taylor]

Hari <hari@cse.iitb.ac.in> writes:

>  I am an undergraduate student at IIT Bombay working on the control flow
> of GCC while compiling c code.I am intrested in tracing the path of gcc
> during compilation.I don't see any good material on this topic anywhere.
>  One approach is to  put break points in all of (176) c files 
> in gcc directory and check the flow but that seems to be very time
> consuming . Is there is anyother way out???

The main path of compiling code is in the function
rest_of_compilation().  It calls a series of passes.  See also the
documentation for the -d option.

Ian

Re: Debugging GCC

[Andrey Belevantsev]

Brendon Costa wrote:
> Does anyone know a way of invoking g++ inside gdb or compiling g++ so 
> that g++ will not handle the SIGSEGV signal but would crash instead so 
> GDB can give me a stack trace of the place where the segmentation fault 
> occurred?
http://gcc.gnu.org/wiki/DebuggingGCC explains how to debug the compiler. 
Also, you can put a breakpoint on fancy_abort() to see what happens when 
an ICE is occured.

Andrey

Debugging GCC

[Brendon Costa]

Hi all,

    I have been working on a small extension to the C++ front end of GCC 
that helps me to document exceptions while compiling code. Anyway my 
extension requires me to modify GCC and so I am modifying version 4.0.1. 
Through developing this I have come across a single frustration that has 
slowed my development down a lot. Basically GCC seems to catch any 
SIGSEGV generated and then spit out an Internal Compiler Error. This is 
ok, I am still trying to debug some of my code that is producing the 
exception, but the problem is that I want to run g++ inside a debugg 
(gdb) in order to find out where the SIGSEV is being generated. 
Currently I have a lot of very extensive logging procedures that try to 
narrow down the problem, but it is still tedious.

Does anyone know a way of invoking g++ inside gdb or compiling g++ so 
that g++ will not handle the SIGSEGV signal but would crash instead so 
GDB can give me a stack trace of the place where the segmentation fault 
occurred?

Thanks,
Brendon.

Re: debugging gcc

[Andrea 'Fyre Wyzard' Bocci]

Heve you had a look at the GCC manuals ?
http://gcc.gnu.org/onlinedocs/gcc/
http://gcc.gnu.org/onlinedocs/gccint/

fwyzard

debugging gcc

[ratnadeep joshi]

hello ,

  i want to know the intermediate representation of gcc and integration of front end - back end of gcc to try to write a small front end for it 

   what can be done for this ? do i have to debug gcc code itself to know its passes and their calling ?
If yes , how to debug gcc code ? How to use gdb or any other debugging tool to debug whole gcc code 

  - ratnadeep