This is the mail archive of the gcc@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: Fwd: GCC debug

From: Andrew Haley <aph at redhat dot com>
To: daniel tian <daniel dot xntian at gmail dot com>
Cc: gcc at gcc dot gnu dot org
Date: Mon, 28 Sep 2009 13:14:46 +0100
Subject: Re: Fwd: GCC debug
References: <121fadb80909280444o7ffc255y4ce27c3ffcb26e8d@mail.gmail.com> <4AC0A269.5080304@starynkevitch.net> <121fadb80909280452y475cac7btea6bafeeb947d762@mail.gmail.com> <4AC0A4E8.1030205@starynkevitch.net> <121fadb80909280507v38ffc685id222096ac846fd44@mail.gmail.com> <121fadb80909280508r6e626055i993a7763d96647a5@mail.gmail.com>

daniel tian wrote:
> 2009/9/28 Basile STARYNKEVITCH <basile@starynkevitch.net>:
>> daniel tian wrote:
>>> Thanks.
>>> But how to debug cc1. Because now I port the gcc to my RISC target.
>>> But when build the libgcc2.c.  Some error occurred. So i have to debug
>>> it.
>>> Any advice about how to debug?
>>
>> Start gdb from the build directory (more precisely from $BUILDIR/gcc)
>>
>> BTW, I am not sure your question belongs to gcc@gcc.gnu.org - it is really a
>> beginner's question, and there are several documents about it.
>>
>> This is why I reply to you only, not to the list.
>>
> Thanks.
> You didn't get my point.
> If I just start up gdb to debug cc1, cc1 will return with message that
> it did't know the parameter I pass to it.

"gcc -v" shows you all the parameters that are passed to cc1.  You need to
use these in gdb.

Andrew.

References:
- GCC debug
  - From: daniel tian
- Re: GCC debug
  - From: daniel tian
- Fwd: GCC debug
  - From: daniel tian

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