This is the mail archive of the gcc-patches@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]

PING Re: [RFA] Let GDB find the right options.c


Ping. Thanks.

Jie

On 03/31/2010 03:59 PM, Jie Zhang wrote:
When I was trying to set a breakpoint on a function in GCC generated
options.c, like cl_optimization_restore, GDB always thought it's the
options.c in gcc/fortran/ . That's because the .gdbinit in the GCC build
directory looks like:

dir .
dir ../../../svn/trunk/gcc
dir ../../../svn/trunk/gcc/ada
dir ../../../svn/trunk/gcc/cp
dir ../../../svn/trunk/gcc/fortran
dir ../../../svn/trunk/gcc/java
dir ../../../svn/trunk/gcc/lto
dir ../../../svn/trunk/gcc/objc
dir ../../../svn/trunk/gcc/objcp
source ../../../svn/trunk/gcc/gdbinit.in

So GDB will search ../../../svn/trunk/gcc/fortran before the build
directory. This patch moves "dir ." after all other dir commands. So the
build directory will be searched first.

The options.c in gcc/fortran should still be able to be found correctly
when setting breakpoint on the functions in that file, since the file
name for that options.c will contains "fortran/"

Is it OK?



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