email.
Sujet:
Bug#525071: fixed in libcrypto++ 5.6.0-2
Expéditeur:
Jens Peter Secher
Date:
Tue, 19 May 2009 08:26:46 +
Destinataire:
525071-cl...@bugs.debian.org
Destinataire:
525071-cl...@bugs.debian.org
Source: libcrypto++
Source-Version: 5.6.0-2
We believe that the bug you report
> I’m CC'ing debian-user in case there are people with i386/unstable/amule
> who can confirm or deny the segfault. Please CC 525...@bugs.debian.org
> if you do so.
>
> Also, do you get any kind of backtrace, or can obtain one?
I can confirm this one, it crashes with a SIGSEGV.
Happens with the dae
The maintainer of libcrypto++ can reproduce the problem and is taking a
look. However, it may take a while. In the meantime, amule will be
unable to migrate to testing.
--
- Are you sure we're good?
- Always.
-- Rory and Lorelai
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@li
Hello all.
Thanks for your report about the current segfault in Debian. I've asked
the libcrypto++ maintiner to help with the issue, since the crash seems
to happen in libcrypto++ code, and he's taking a look at the issue. I'll
keep you updated about any progress.
Cheers,
--
- Are you sure we'r
Um 16:41 Uhr am 24.04.09 schrieb Sven Hartge:
> I modified the amule-sources to include an amule-dbg package and managed
> to grab the following backtrace. It is not perfect, libcrypto8++ misses a
> debug package as well.
Now I've added a debug package to libcrypto as well and got an even better
merge 525184 525071
thanks
Hi!
I modified the amule-sources to include an amule-dbg package and managed
to grab the following backtrace. It is not perfect, libcrypto8++ misses a
debug package as well.
#0 0x89fedbd5 in ?? ()
No symbol table info available.
#1 0xffedf57a in ?? ()
No symbol tabl
On Wed, Apr 22, 2009 at 09:56:51AM +0200, Adeodato Sim?? wrote:
> + Claudio Saavedra (Wed, 22 Apr 2009 10:49:35 +0300):
>
> > FWIW, I can confirm this bug. amule crashes on me on startup. The
> > stacktrace is the same.
>
> On i386, I assume?
That's correct.
--
To UNSUBSCRIBE, email to debi
+ Claudio Saavedra (Wed, 22 Apr 2009 10:49:35 +0300):
> FWIW, I can confirm this bug. amule crashes on me on startup. The
> stacktrace is the same.
On i386, I assume?
--
- Are you sure we're good?
- Always.
-- Rory and Lorelai
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@li
FWIW, I can confirm this bug. amule crashes on me on startup. The
stacktrace is the same.
Claudio
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On Втр, 2009-04-21 at 23:50 +0200, Adeodato Simó wrote:
> + Stanislav Maslovski (Wed, 22 Apr 2009 01:37:09 +0400):
>
> > Package: amule
> > Version: 2.2.4-1+b1
> > Severity: normal
>
> > For your information: after todays upgrade to automatically rebuilt
> > amule 2.2.4-1+b1 it segfaults on start
+ Stanislav Maslovski (Wed, 22 Apr 2009 01:37:09 +0400):
> Package: amule
> Version: 2.2.4-1+b1
> Severity: normal
> For your information: after todays upgrade to automatically rebuilt
> amule 2.2.4-1+b1 it segfaults on start. The problem seems to be related
> with libcrypto++8, as returning back
Package: amule
Version: 2.2.4-1+b1
Severity: normal
For your information: after todays upgrade to automatically rebuilt
amule 2.2.4-1+b1 it segfaults on start. The problem seems to be related
with libcrypto++8, as returning back to 2.2.4-1 built with libcrypto++7
solves the problem.
-- System In
12 matches
Mail list logo
