From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30933 invoked by alias); 21 Dec 2013 05:46:31 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 30921 invoked by uid 89); 21 Dec 2013 05:46:30 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-lb0-f182.google.com Received: from mail-lb0-f182.google.com (HELO mail-lb0-f182.google.com) (209.85.217.182) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Sat, 21 Dec 2013 05:46:29 +0000 Received: by mail-lb0-f182.google.com with SMTP id l4so1429068lbv.41 for ; Fri, 20 Dec 2013 21:46:25 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=39SYnPt44VSm54+7JU1vS2nGPuyogR02E9OezyXCOnk=; b=WslaisKKY28hthFaMgvnzDtTD/WQ5Nv0+H9KEyGAlx3IyytZlgeJgTLofU3i2isOfg Qe2+AdSbFSQShnt2JyMyrTsTQN9P3zkW/9TWDOCxs4tRx7eIi5zlU5KsPFarcg8c1rzv obTv5fbRAn1Mgom93LR/ph2raLvfKwifCF9i7EzaamigYx1pYEP0cM7RgDYhipdR7WoS 7hB3zRCVF/91OKJJR1b8AgNuXRvPrXddcAnxFdI1PBdcD4BVjBBWj93uuH2sbzyZM79U 8PJmRgrxDWiFzWzlSNKetqhDc+WNtUgwe2Bc0KE592dR+oLOjVbO0GecpLJKu7P4ZXd5 i7XQ== X-Gm-Message-State: ALoCoQktuEJQoO1aVzuSJuNQOUsSh0xyoZsEEsujyUhU27vmc2iGHubx8GKEcZaNrwTTxO54S3mX6Qa339N/yWYkmbSsNP0Z8LIM8x0S/kk03vAj/vGTvgFo60OkkiLA0Tr5ZC/Egovw MIME-Version: 1.0 X-Received: by 10.112.218.74 with SMTP id pe10mr5179064lbc.19.1387604785635; Fri, 20 Dec 2013 21:46:25 -0800 (PST) Received: by 10.152.182.201 with HTTP; Fri, 20 Dec 2013 21:46:25 -0800 (PST) In-Reply-To: <201312201441.24149.vapier@gentoo.org> References: <201312201441.24149.vapier@gentoo.org> Date: Sat, 21 Dec 2013 05:46:00 -0000 Message-ID: Subject: Re: Kernel debugging From: Nikos Balkanas To: Mike Frysinger Cc: gdb@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes X-SW-Source: 2013-12/txt/msg00072.txt.bz2 Ty mike, I am aware of kdgb, but it doesn't have gdb's abilities. Besides I know extensibly gdb, and I can never find the Sysreq key on my keyboard :-(. I will try it next time, but for now I solved my problem by reading the kernel source code. I have noticed the remote_vis.c in gdb sources. Does this mean I can use gdb remotely to a virtual host? How can i do it? Furthermore have gdbstubs incorporated into gdb sources, or is it another abandoned project (since 2003 :-()? Nikos On Fri, Dec 20, 2013 at 9:41 PM, Mike Frysinger wrote: > On Thursday 19 December 2013 13:51:36 Nikos Balkanas wrote: >> I am developing a module for the Linux kernel. For that i have setup >> the exact environment in Virtual Box and have loaded the (guest) >> kernel with -g and removed the -frame-pointers. I will run gdb from >> host and try to debug kernel on guest system. >> >> What is the best approach for this scenario? GDBserver or gdbstubs?. >> Gdb server is good only for userspace debugging. Will gdbstubs work? >> Are they included in the recent gdb sources, or are the ones to use >> since 2003 from sourceforge? I am also looking for instructions on how >> to implement them. Any hints? > > the kernel has a built in gdb stub. look for "kgdb" in the > documentation/kconfig. > -mike