From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-37513-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 11261 invoked by alias); 12 Jun 2010 15:19:36 -0000
Received: (qmail 11253 invoked by uid 22791); 12 Jun 2010 15:19:36 -0000
X-SWARE-Spam-Status: No, hits=-1.5 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM
X-Spam-Check-By: sourceware.org
Received: from mail-ww0-f41.google.com (HELO mail-ww0-f41.google.com) (74.125.82.41)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 12 Jun 2010 15:19:32 +0000
Received: by wwb34 with SMTP id 34so2202403wwb.0        for <gdb@sourceware.org>; Sat, 12 Jun 2010 08:19:29 -0700 (PDT)
Received: by 10.216.185.10 with SMTP id t10mr498417wem.32.1276355969614;        Sat, 12 Jun 2010 08:19:29 -0700 (PDT)
Received: from [192.168.0.12] (dra38-7-88-179-85-53.fbx.proxad.net [88.179.85.53])        by mx.google.com with ESMTPS id n29sm828647wej.41.2010.06.12.08.19.27        (version=SSLv3 cipher=RC4-MD5);        Sat, 12 Jun 2010 08:19:28 -0700 (PDT)
Subject: Re: Backtrace from kernel to user space in coredump
From: =?ISO-8859-1?Q?Fr=E9d=E9ric?= RISS <frederic.riss@gmail.com>
To: Michael Eager <eager@eagerm.com>
Cc: gdb@sourceware.org
In-Reply-To: <4C138642.2080202@eagerm.com>
References: <4C138642.2080202@eagerm.com>
Content-Type: text/plain; charset="UTF-8"
Date: Sat, 12 Jun 2010 15:19:00 -0000
Message-ID: <1276355966.1798.3.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2010-06/txt/msg00042.txt.bz2

Le samedi 12 juin 2010 à 06:06 -0700, Michael Eager a écrit :
> Are there better ways to do this?   How have other
> people handled traces back from kernel to user space?

It's more heavyweight than just setting the registers, but it's quite
easy to add specific unwinders for syscalls, exceptions, interrupts...
And this works very nicely (well, the real difficulty is to have GDB
load the debug information for the appropriate userspace task, but
that's maybe not an issue in your case).

Fred