From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from outbound.mse2.exchange.ms ([69.25.50.247] helo=mse2fe1.mse2.exchange.ms) by pentafluge.infradead.org with esmtp (Exim 4.63 #1 (Red Hat Linux)) id 1IbNeW-0000oD-QD for kexec@lists.infradead.org; Fri, 28 Sep 2007 22:45:44 +0100 Message-ID: <46FD75E1.3090602@bluelane.com> Date: Fri, 28 Sep 2007 14:45:05 -0700 From: Pete/Piet Delaney MIME-Version: 1.0 Subject: Re: [Kgdb-bugreport] Problem getting kgdb to read kernel symbols. addresses shifted? References: <46FD03CD.9060404@windriver.com> <46FD1B6A.3000500@windriver.com> <20070928114522.n0cdrcebykkgg408@webmail.mit.edu> <46FD2CFB.9010404@windriver.com> In-Reply-To: <46FD2CFB.9010404@windriver.com> Reply-To: pete@bluelane.com List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: kexec-bounces@lists.infradead.org Errors-To: kexec-bounces@lists.infradead.org To: Jason Wessel Cc: Derek Atkins , kgdb-bugreport@lists.sourceforge.net, Dave Anderson , "Eric W. Biederman" Jason Wessel wrote: Shouldn't crash, kdump and kgdb take into consideration a shift in the kernel so that gdb works normally? Seems that having the kgdb stub knowledgeable of a shift in the kernel might be easy to compensate for. Perhaps just mapping all reads and writes that lie within the original kernel segments to the shifted addresses. -piet > Derek Atkins wrote: >> Quoting Jason Wessel : >> >>>> Um, okay..... How do I do that? My GDB Fu is weak here; how do I >>>> tell gdb that the symbols in vmlinux are all offset? Or how do I >>>> manipulate the vmlinux binary to offset the symbols? >>>> >>> Start gdb with no file. And do something like: add-symbol-file vmlinux >>> 0xBFA00000 >> Um, where did you get "0xBFA0000" from? Unfortunately this didn't >> work at all. I would think to get my numbers to work I'd need to >> use 0xC0400000 to get sys_close to appear at 0xc047d341. And >> viola, that seems to work! Or at least I got a reasonable breakpoint >> from the 'target remote' > > It was an example. You had previously stated it was an offset of > 0x600000 so it was a subtraction of 0x600000 from 0xc0000000. > > Jaosn. > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Kgdb-bugreport mailing list > Kgdb-bugreport@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport > _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec