Hi Marek, On Mar 4, 2004, at 11:16 PM, Marek Kozubal wrote: Hello! I've been doing 2 machine debugging for a while now. One of the machines I am trying to debug however has become a pain. It won't let me do proper back traces or other features in kgm_macros either. Both machines are running 10.2.8 and both machines have the developer tools installed (dec '03 for jaguar). I've also tried it from another machine or 2 with the same results. For example, using the 10.2.8 kernel debug disk image from Apple: [villain:~] marek% gdb /Volumes/KernelDebugKit/mach_kernel GNU gdb 5.3-20021014 (Apple version gdb-250) (Sat Dec 7 02:14:27 GMT 2002) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "powerpc-apple-macos10". (gdb) source /Volumes/KernelDebugKit/kgmacros Loading Kernel GDB Macros package. Type "help kgm" for more info. (gdb) target remote-kdp (gdb) attach 10.0.0.3 Connected. [Switching to process 3] (gdb) showpid 434 /* this is the Finder's PID */ task vm_map ipc_space #acts pid proc command Cannot access memory at address 0x154 (gdb) showalltasks task vm_map ipc_space #acts pid proc command Cannot access memory at address 0x0 Is there some setting, or version mis-match that would cause these Macro's not to work? This does sound like a version mismatch between the Kernel Debug Kit you're using and the kernel running on the target system. The two must be the same version. This is covered in the ReadMe included with each Kernel Debug Kit. Note that there are two Kernel Debug Kits for Mac OS X 10.2.8: one for the G5, and another for everything else. Double-check the build number in About this Mac or System Profiler: the G5 build of 10.2.8 was 6S90. The machine has Panther installed on other partitions, I've done the usual boot-args="debug=0xe" and making the arp entry perminate and all that. That only affects GDB's ability to attach to another system's kernel. It has no effect on the kgmacros. The macros rely on the symbols in mach_kernel. However, this and other issues (like bt not working properly, not being able to inspect variables when bt does seem to work) is making things quite hard to track down. So if anyone has any ideas, it'd be most helpful! Thanks in advance! --- Marek Kozubal marek@portents.com HTH, --gc _______________________________________________ darwin-kernel mailing list | darwin-kernel@lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-kernel Do not post admin requests to the list. They will be ignored.