From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261787AbUDWX5c (ORCPT ); Fri, 23 Apr 2004 19:57:32 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261790AbUDWX5c (ORCPT ); Fri, 23 Apr 2004 19:57:32 -0400 Received: from ns.suse.de ([195.135.220.2]:20173 "EHLO Cantor.suse.de") by vger.kernel.org with ESMTP id S261787AbUDWX5b (ORCPT ); Fri, 23 Apr 2004 19:57:31 -0400 Date: Sat, 24 Apr 2004 01:55:21 +0200 From: Olaf Dabrunz To: Jim Houston Cc: linux-kernel@vger.kernel.org Subject: kernel trace (with KDB) Message-ID: <20040423235521.GA19942@suse.de> Mail-Followup-To: Jim Houston , linux-kernel@vger.kernel.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hello, you once submitted a patch implementing a "kernel trace mechanism for KDB". Do you have a current version of this patch for 2.6 kernels? Will function call tracing ever be integrated into KDB? Regards, -- Olaf Dabrunz (od/odabrunz), SUSE Linux AG, Nürnberg