This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.

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: Debugging the gcc compiler using gdb

From: Daniel Kegel <dank at kegel dot com>
To: Surupa Biswas <surupa_biswas at hotmail dot com>
Cc: crossgcc at sources dot redhat dot com
Date: Mon, 23 Feb 2004 10:30:43 -0800
Subject: Re: Debugging the gcc compiler using gdb
References: <BAY2-F169RJLH27BCm50002be6e@hotmail.com>

Surupa Biswas wrote:

I am trying to debug the gcc 3.2 compiler for mcore under gdb 5.2.1-2mdk (on Mandrake 9.1). I want to set breakpoints on some functions inside a particular file that I have written and integrated into the compiler. I run gdb gcc-mcore when I type break my_func, it says function not defined. So, I do add-symbol-file my_file and now if I type break my_func, it says error accessing memory at adress xyz (I have verified by looking at the object dump that the address does correspond to my_func)

How do I run gcc-mcore and have breakpoints inside my_file ?


I dunno, but I know that fairly often I have to set a breakpoint
on main, run, stop at main, and *then* set breakpoints on
what I care about.  That way more symbol tables are loaded...
- Dan

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com

References:
- Debugging the gcc compiler using gdb
  - From: Surupa Biswas

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