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

Bug#587938: mimedecode exits with: *** glibc detected *** mimedecode: malloc(): memory corruption: 0x0811f138 ***

Package: mimedecode
Version: 1.9-4
Severity: normal

Hello Maintainer,

I use "procmail" and since it can not decode it self, I  use  mimedecode
for it since years.  but now I get tonns of 

*** glibc detected *** mimedecode: malloc(): memory corruption: 0x0811f138 ***

if I run

----[ command 'mimedecode <1278109783.28706_1.samba3' ]-----------------

Return-Path: <openocd-development-bounces@lists.berlios.de>
X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on
X-Spam-Status: No, score=-0.2 required=4.5 tests=AWL,BAD_ENC_HEADER,BAYES_00,
        DNS_FROM_OPENWHOIS,HTML_MESSAGE autolearn=no version=3.2.3
Delivered-To: XXXXXXX.ml4michelle@tamaXXXogan.net
Received: from mail.berlios.de (bat.berlios.de [::ffff:])
  by mail.tamay-dogan.net with esmtp; Tue, 29 Jun 2010 11:33:34 +0200
  id 0002BDBC.4C29BDEE.00001D9B
Received: from bat.berlios.de (unknown [IPv6:::1])
        by mail.berlios.de (Postfix) with ESMTP id 9EE3E227AD;
        Tue, 29 Jun 2010 11:33:00 +0200 (CEST)
X-Original-To: openocd-development@lists.berlios.de
Delivered-To: openocd-development@lists.berlios.de
Received: from n23.bullet.mail.ukl.yahoo.com (n23.bullet.mail.ukl.yahoo.com
        by mail.berlios.de (Postfix) with SMTP id A0684223D2
        for <openocd-development@lists.berlios.de>;
        Tue, 29 Jun 2010 11:32:58 +0200 (CEST)
Received: from [] by n23.bullet.mail.ukl.yahoo.com with NNFMP;
        29 Jun 2010 09:32:58 -0000
Received: from [] by t1.bullet.ukl.yahoo.com with NNFMP;
        29 Jun 2010 09:32:58 -0000
Received: from [] by omp232.mail.ukl.yahoo.com with NNFMP;
        29 Jun 2010 09:32:58 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 318765.71192.bm@omp232.mail.ukl.yahoo.com
Received: (qmail 72748 invoked by uid 60001); 29 Jun 2010 09:32:58 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.fr; s=s1024;
        t=1277803978; bh=TEXGjuwkkonov3SV826yYP1fyG94MDeWColtxgXN0v0=;
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.fr;
Message-ID: <210720.71839.qm@web25808.mail.ukl.yahoo.com>
X-YMail-OSG: zmrh93MVM1nCydpyaL1Fsu8sXj56DW.GxpJ2he16aLMBseo
Received: from [] by web25808.mail.ukl.yahoo.com via HTTP;
        Tue, 29 Jun 2010 09:32:57 GMT
X-Mailer: YahooMailClassic/11.1.4 YahooMailWebService/
Date: Tue, 29 Jun 2010 09:32:57 +0000 (GMT)
From: cedric libre <cedric_libre@yahoo.fr>
To: freddie_chopin@op.pl
In-Reply-To: <Q6613466-75d0c3fb1a86422afad14394eab5f68f@pmq4.m5r2.onet.test.onet.pl>
MIME-Version: 1.0
Cc: openocd-development@lists.berlios.de
*** glibc detected *** mimedecode: malloc(): memory corruption: 0x08d4a138 ***
======= Backtrace: =========
======= Memory map: ========
08048000-0804c000 r-xp 00000000 08:05 146152     /usr/bin/mimedecode
0804c000-0804d000 rw-p 00003000 08:05 146152     /usr/bin/mimedecode
08d4a000-08d6b000 rw-p 08d4a000 00:00 0          [heap]
b7c00000-b7c21000 rw-p b7c00000 00:00 0
b7c21000-b7d00000 ---p b7c21000 00:00 0
b7d62000-b7d6e000 r-xp 00000000 08:05 236157     /lib/libgcc_s.so.1
b7d6e000-b7d6f000 rw-p 0000bAbgebrochen (core dumped)

Attached the message which cause this error

Thanks, Greetings and nice Day/Evening
    Michelle Konzack

##################### Debian GNU/Linux Consultant ######################
   Development of Intranet and Embedded Systems with Debian GNU/Linux

itsystems@tdnet France EURL       itsystems@tdnet UG (limited liability)
Owner Michelle Konzack            Owner Michelle Konzack

Apt. 917 (homeoffice)
50, rue de Soultz                 Kinzigstraße 17
67100 Strasbourg/France           77694 Kehl/Germany
Tel: +33-6-61925193 mobil         Tel: +49-177-9351947 mobil
Tel: +33-9-52705884 fix

<http://www.itsystems.tamay-dogan.net/>  <http://www.flexray4linux.org/>
<http://www.debian.tamay-dogan.net/>         <http://www.can4linux.org/>

Jabber linux4michelle@jabber.ccc.de
ICQ    #328449886

Linux-User #280138 with the Linux Counter, http://counter.li.org/
--- Begin Message ---
Hi ,

I have once more ( :-)  tried to install the drivers but this time, I have
 copied first libusb0.dll in \WINDOWS\system32 and then I succeeded the installation !!
Now, I still have a problem , as I plug the device and run this command :
 openocd.exe -f interface\jtagkey-tiny.cfg   : 
Error: unable to open ftdi device: unable to claim usb device . Make sure ftdi_sio is unloaded !

What does that mean ?

Thanks all for your help


--- En date de : Mar 29.6.10, freddie_chopin@op.pl <freddie_chopin@op.pl> a écrit :

De: freddie_chopin@op.pl <freddie_chopin@op.pl>
Objet: =?ISO-8859-2?Q?Re: [Openocd-development] Re : Openocd-development Digest, Vol 45, Issue 44=ina?=
À: openocd-development@lists.berlios.de, "cedric libre" <cedric_libre@yahoo.fr>
Date: Mardi 29 juin 2010, 10h54


After installing OpenOCD extract the file c:\Program Files\OpenOCD\0.4.0\drivers\libusb-win32_ft2232_driver-100223.zip and follow the instructions in info.txt. This package has functional libusb-win32 drivers for JTAGkey.

When searching for drivers point the wizard (with the "Have Disk" button) to the directory containing libusb-win32_ft2232_driver.inf.

Have in mind that FT2232 is a composite device which normally takes 3-5 drivers:
- Composite Device - this uses generic Windows driver (this usually does not require any Wizard and is installed automatically)
- first channel (Channel A - usually JTAG interface)
- second channel (Channel B - usually USB Serial Port or unused)

if first or second channel are configured as serial port, additional drivers will be required for "USB Serial Port".

Your JTAGkey should require 3 drivers - Composite Device (automatic) and 2x libusb-win32 from the package bundled with OpenOCD installer.

Do note, that once you installed ftd2xx drivers you have to remove the ones you wish to replace or - as Xiaofan said - you can manually "update" them. You only need to manipulate with the first channel, as OpenOCD doesn't care about the second channel (whether or not it's actually used for anything).


Openocd-development mailing list

--- End Message ---

Attachment: signature.pgp
Description: Digital signature

Reply to: