From owner-kgdb@oss.sgi.com Mon Mar 6 11:23:08 2000 Received: by oss.sgi.com id ; Mon, 6 Mar 2000 11:22:58 -0800 Received: from mtigate.mti.com ([144.86.1.1]:55748 "EHLO mtigate.mti.com") by oss.sgi.com with ESMTP id ; Mon, 6 Mar 2000 11:22:37 -0800 Received: from ccmgate.mti.com (ccmgate [144.86.14.157]) by mtigate.mti.com (8.8.8/8.8.8) with SMTP id LAA24083 for ; Mon, 6 Mar 2000 11:21:55 -0800 (PST) From: LWisneski@mti.com Received: from ccMail by ccmgate.mti.com (ccMail Link to SMTP R8.31.00.5) id AA952370864; Mon, 06 Mar 2000 11:27:48 -0800 Message-Id: <0003069523.AA952370864@ccmgate.mti.com> X-Mailer: ccMail Link to SMTP R8.31.00.5 Date: Mon, 06 Mar 2000 11:18:32 -0800 To: Subject: KGDB Question MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Description: "cc:Mail Note Part" Sender: owner-kgdb@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;kgdb-outgoing Hi, I'm new to this list, so if I repeat a question that's already been addressed, sorry. I've looked thru the archives and didn't find anything that would help me. I'm attempting to install kGDB on my machine (P-II 400MHz) which is running Caldera 2.3 linux (kernel version is 2.2.10). I downloaded the kdb-v0.5-2.2.10.gz file, and applied it, ran the xconfig, and the rebuilt the kernel. I then rebooted, and I received an error message in the log file which states: kdb: Exceeded symbol size. Increase KDBSYMTABSIZE in scripts/genkdbsym.awk which I do. I increased it from 7500 to 8500, rebuild the kernel, etc., and boot from the new image which starts the kernel load/execution, and then it (apparently) dies and reboots the machine. Sounds like I stepped on some piece of memory somewhere. Has anyone seen this before? If so, how does one resolve it? If no one has seen this before, and pointers on how to figure out what's going on? Thanks, Larry Wisneski MTI From owner-kgdb@oss.sgi.com Fri Mar 31 16:38:50 2000 Received: by oss.sgi.com id ; Fri, 31 Mar 2000 16:38:41 -0800 Received: from sentry.gw.tislabs.com ([192.94.214.100]:9160 "EHLO sentry.gw.tislabs.com") by oss.sgi.com with ESMTP id ; Fri, 31 Mar 2000 16:38:29 -0800 Received: by sentry.gw.tislabs.com; id TAA23413; Fri, 31 Mar 2000 19:40:04 -0500 (EST) Received: from clipper.gw.tislabs.com(10.33.1.2) by sentry.gw.tislabs.com via smap (V5.5) id xma023411; Fri, 31 Mar 00 19:40:02 -0500 Received: from dustpuppy.va.tislabs.com (IDENT:root@dustpuppy.va.tislabs.com [192.168.10.114]) by clipper.gw.tislabs.com (8.9.3/8.9.1) with ESMTP id TAA20742 for ; Fri, 31 Mar 2000 19:37:12 -0500 (EST) Received: from localhost (dougk@localhost) by dustpuppy.va.tislabs.com (8.9.3/8.8.7) with ESMTP id TAA09909 for ; Fri, 31 Mar 2000 19:42:25 -0500 X-Authentication-Warning: dustpuppy.va.tislabs.com: dougk owned process doing -bs Date: Fri, 31 Mar 2000 19:42:25 -0500 (EST) From: Douglas Kilpatrick X-Sender: dougk@dustpuppy.va.tislabs.com To: kgdb@oss.sgi.com Subject: kgdb and 2.2.14-5 from RH 6-2. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-kgdb@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;kgdb-outgoing First the easy stuff: init/main.c: The patch reads: + if (!strcmp(line,"gdbttyS=")) { + gdb_ttyS = simple_strtoul(line+8,NULL,10); + continue; + } + if (!strcmp(line,"gdbbaud=")) { + gdb_baud = simple_strtoul(line+8,NULL,10); + continue; + } Those are, of course, supposed to be: if (!strncmp(line,"gdbttyS=",8)) { Also, since going into the debugger at any arbitrary point is usefull I added a few lines to sysrq.c. Sorry this isn't in patch format but I'm trying to do module development not kernel development and so don't have a clean copy of kernel source to diff. Anyway, at line 31, after the CONFIG_APM section: #ifdef CONFIG_GDB extern int gdb_hook(void); #endif and at line 141, after the case 'l' section: #ifdef CONFIG_GDB case 'g': gdb_hook(); break; #endif Now for the more fundamental issue: Attaching to the debugger appears to work, but as soon as I continue from gdb, the system Oops', then panics and locks. Things never get sent back into gdb, and it crashes too quickly for syslog to write out the oops message so I don't know what the stack looks like yet. This happens if I attach at boot or via sysctl, so I'm pretty sure its not something I've done. If it matters, I can provide my .config, but basically its a RH6.2 stock (as if) kernel with SCSI/sound/RAID/stuff I don't need removed, and the kgdb0.2-2.2.12 patch applied. (Minus the root-level makefile changes that somehow made it into the RH 2.2.14 kernel) Any ideas? Anyone seen this before? Doug -- dougk@tislabs.com dkilpatr@nai.com Will crash Linux for food.