From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8657 invoked by alias); 21 Oct 2002 14:59:43 -0000 Mailing-List: contact insight-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sources.redhat.com Received: (qmail 8649 invoked from network); 21 Oct 2002 14:59:43 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 21 Oct 2002 14:59:43 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id g9LEcUw01905 for ; Mon, 21 Oct 2002 10:38:30 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id g9LExgf27223; Mon, 21 Oct 2002 10:59:42 -0400 Received: from valrhona.uglyboxes.com (IDENT:qTUcMxazJapJxmT0Y8Jmqd4roqKBqjd+@vpn50-44.rdu.redhat.com [172.16.50.44]) by pobox.corp.redhat.com (8.11.6/8.11.6) with ESMTP id g9LExfT20559; Mon, 21 Oct 2002 10:59:41 -0400 Date: Mon, 21 Oct 2002 07:59:00 -0000 From: Keith Seitz X-X-Sender: keiths@valrhona.uglyboxes.com To: weiming liu cc: insight@sources.redhat.com Subject: Re: Insight and KGDB In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-q4/txt/msg00049.txt.bz2 [Moved to list -- others may be interested to know what you're up to] On Mon, 21 Oct 2002, weiming liu wrote: > Insight is a great tool for kernel debug. I tried to integrate > kgdb(kgdb.sourceforge.net) and Insight( on MS win2000) to debug a linux > kernel file system. Connection and breakpoint are ok. But source mode of > source window doesn't work. It's automatically changed into assembly mode. > I open vmlinux with file/open menu. What's wrong ? Could you give me a hand > to address this issue? Insight will automatically switch to assembly mode when it cannot find the source files for a given module. The first step is to determine if your image has debug info and whether gdb can find/parse that info. We'll need much more info about the executable you're attempting to debug. I presume your stopped in a C function? If so, what does gdb say about this function? ("info func FUNCTION_NAME") If you're NOT stopped at a function but in an assembler source file, what does gdb say about it? (try "list ASM_FILE:1") Keith