On Tue, Feb 24, 2009 at 4:38 PM, Vincent R. <foru...@smartmobili.com> wrote:
> Hi,
>
> even if I am simple mortal I would like to understand or at least follow
> what is going on with gcc.
> Generally when I run gdb and try to breakpoint inside a function I get a
> undefined symbol or something like that.
> I suppose this is because gcc is not a simple static exe but depends on
> other binaries (g++, cpp, ...).
> So my question is how can I debug step by step gcc ?
> Let's say for instance I want to breakpoint the function
> init_exception_processing located in gcc/gcc/cp
> and related to c++ exceptions
>
> This GDB was configured as "i486-linux-gnu"...
> (gdb) b init_exception_processing
> Function "init_exception_processing" not defined.
> Make breakpoint pending on future shared library load? (y or [n])
>
> What is the magical trick to be able to follow what is going on.

You are probably debugging the driver - try debugging the compiler
(called cc1, cc1plus).  The command-line is printed if you execute
gcc with the extra -v switch.

Richard.

Reply via email to