linux-mips
[Top] [All Lists]

Re: remote GDB debugging and the __init macro of init.h

To: "Kevin D. Kissell" <kevink@mips.com>
Subject: Re: remote GDB debugging and the __init macro of init.h
From: Ralf Baechle <ralf@oss.sgi.com>
Date: Sat, 28 Oct 2000 03:53:16 +0200
Cc: Steve Kranz <skranz@ridgerun.com>, linux-mips@oss.sgi.com, linux-mips@fnet.fr
In-reply-to: <014a01c0402d$b432ada0$0deca8c0@Ulysses>; from kevink@mips.com on Fri, Oct 27, 2000 at 05:50:50PM +0200
References: <39F99E20.8EE47072@ridgerun.com> <014a01c0402d$b432ada0$0deca8c0@Ulysses>
Sender: owner-linux-mips@oss.sgi.com
On Fri, Oct 27, 2000 at 05:50:50PM +0200, Kevin D. Kissell wrote:

> What you've done should solve the problem, but note
> that it has the side effect of preventing the text and data
> sections in question from getting freed up at the end
> of initialization.  I probably should have done so myself
> last year when I was struggling with debugging some init 
> code using kgdb, but instead I simply got used to finding 
> the address in the symbol table and setting the breakpoints 
> by hex address instead of by symbol.
> 
> The real fix would be to  teach gdb to treat symbols
> in the init section as valid targets.

Did somebody look into porting KDB?

  Ralf

<Prev in Thread] Current Thread [Next in Thread>