reopen 449207
thanks
On 11/30/07, Andrew Moise <[EMAIL PROTECTED]> wrote:
> Hm, I'm not able to reproduce it with version 0.9.1-1+b1. Either
> some fix made its way into that build or I'm no longer able to
> reconstruct the steps that led it to seg fault.
> I believe that this bug can be clos
On 11/22/07, Frank S. Thomas <[EMAIL PROTECTED]> wrote:
> I tried to reproduce this, but I couldn't. Maybe you could give more details
> how to reproduce this segfault. Here is what I did:
Hm, I'm not able to reproduce it with version 0.9.1-1+b1. Either
some fix made its way into that build or
package curlftpfs
tags 449207 + unreproducible moreinfo
stop
Hello,
On Sunday 04 November 2007, Andrew Moise wrote:
> While trying to track down some other trouble with curlftpfs, I ran the
> daemon under gdb and discovered that it seg faults on exit:
>
> Program received signal SIGSEGV, Segmen
Package: curlftpfs
Version: 0.9.1-1
Severity: normal
While trying to track down some other trouble with curlftpfs, I ran the
daemon under gdb and discovered that it seg faults on exit:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1213983056 (LWP 481)]
0xb7e9d105 in
4 matches
Mail list logo