synaptic-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Synaptic-devel] Strange segfault


From: Panu Matilainen
Subject: Re: [Synaptic-devel] Strange segfault
Date: Thu, 15 Apr 2004 19:09:17 +0300

On Thu, 2004-04-15 at 20:56, Andrey Tarassov wrote:
> Hi!
> 
> I have encountered a very strange problem with synaptic? Namely, we have 
> a repository that may be accessed from both http and ftp using the same 
> address and the repository is signed with GPG.
> 
> Now, the problem is that if you press the refresh button on startup 
> (after some time this is not even required) and edit repositories, 
> pressing refresh again causes synaptic to crash.
> 
> There is only one thing I am editing in repositories: ftp -> http and 
> vice versa. Nothing else. I also encountered this problem before with 
> some other changes, but know I have found a possibility to reproduce the 
> bug easily.
> 
> I looked deeper into the problem and tried to trace the problem with 
> gdb. I found that the segfault appeared in pkgAcqIndexRel::Done(), but 
> could not find why it was happening as everything seemed to be ok.
> 
> Have you heard about such a problem and does anyone know about how to 
> solve it?
> 
> FYI, I am using synaptic-0.48.1 and apt-rpm 0.15.5cnc6.

That sounds a whole lot like a longstanding problem I'm seeing with
apt-shell together with signed repositories:

When running "update" from apt-shell, by the time it gets to 
pkgAcqIndexRel::Done(), Repository->Vendor->FingerPrint has turned into 
garbage, causing the segfault on comparison to Release fingerprint.
Actually most of the Vendor stucture gets overwritten by something, it
seems consistent that the corruption begins at the last character of
Vendor->Description (but not 100% sure about that), anyway the entire
Vendor Repository->Vendor struct get garbled useless.

Doesn't happen with synaptic in my environment but it sounds all too
familiar - can you post the entire backtrace of the crash so we can see
whether it's the same problem or something else?

        - Panu -





reply via email to

[Prev in Thread] Current Thread [Next in Thread]