From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29871 invoked by alias); 21 Jul 2008 02:25:24 -0000 Received: (qmail 29843 invoked by uid 22791); 21 Jul 2008 02:25:23 -0000 X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.33.17) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 21 Jul 2008 02:25:06 +0000 Received: from wpaz13.hot.corp.google.com (wpaz13.hot.corp.google.com [172.24.198.77]) by smtp-out.google.com with ESMTP id m6L2OvIm008919 for ; Mon, 21 Jul 2008 03:24:58 +0100 Received: from yw-out-2324.google.com (ywe9.prod.google.com [10.192.5.9]) by wpaz13.hot.corp.google.com with ESMTP id m6L2Ou6c008963 for ; Sun, 20 Jul 2008 19:24:57 -0700 Received: by yw-out-2324.google.com with SMTP id 9so425883ywe.1 for ; Sun, 20 Jul 2008 19:24:56 -0700 (PDT) Received: by 10.151.108.15 with SMTP id k15mr3209660ybm.88.1216607096390; Sun, 20 Jul 2008 19:24:56 -0700 (PDT) Received: by 10.151.107.3 with HTTP; Sun, 20 Jul 2008 19:24:56 -0700 (PDT) Message-ID: <8ac60eac0807201924r6d741bc1y5a0cb2119662095@mail.gmail.com> Date: Mon, 21 Jul 2008 03:43:00 -0000 From: "Paul Pluzhnikov" To: "Jelle de Jong" Subject: Re: how can i stop a running process to do a backtrace? Cc: gdb@sourceware.org In-Reply-To: <48837E4E.8000202@powercraft.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <488200CC.6000900@powercraft.nl> <20080719150017.GA18314@caradoc.them.org> <4882023D.5090705@powercraft.nl> <8ac60eac0807190936y4ab3ca10j7252c54668808290@mail.gmail.com> <48837E4E.8000202@powercraft.nl> X-IsSubscribed: yes 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 X-SW-Source: 2008-07/txt/msg00235.txt.bz2 On Sun, Jul 20, 2008 at 11:05 AM, Jelle de Jong wrote: > I managed to create three backtraces after the sshfs program froze. I > attached one of them as example. I something is obvious wrong with the > report please tell me. I am no expert to FUSE, and this doesn't belong on this list, but I think your stack trace simply means that sshfs is blocked waiting for 'sftp' to finish whatever it is doing. As such, it will likely be of very little use to sshfs developers; you'll need to see whether the are any sftp or ssh processes, and if so what *they* are blocked on. And if they aren't blocked, then maybe you just need to be more patient -- after all, sshfs can't be any faster than the underlying transport, can it? -- Paul Pluzhnikov