[MacPorts] #10027: BUG: id3v2-0.1.11 malloc errors
MacPorts
noreply at macports.org
Mon Oct 20 16:38:10 PDT 2008
#10027: BUG: id3v2-0.1.11 malloc errors
--------------------------------+-------------------------------------------
Reporter: duke at spacebox.net | Owner: macports-tickets at lists.macosforge.org
Type: defect | Status: closed
Priority: Normal | Milestone: Port Bugs
Component: ports | Version: 1.2
Resolution: invalid | Keywords:
Port: id3v2 |
--------------------------------+-------------------------------------------
Changes (by blb at macports.org):
* status: new => closed
* resolution: => invalid
* port: => id3v2
Old description:
> I installed the id3v2 port and upon using it got an error like the
> following for each file I processed:
>
> id3v2(22560) malloc: *** Deallocation of a pointer not malloced:
> 0x90001c7a; This could be a double free(), or free() called with the
> middle of an allocated block; Try setting environment variable MallocHelp
> to see tools to help debug
>
> I was initially using the id3v2 options [aAtTyg]. I narrowed the problem
> down to the track number option "-T". I tried the following three
> formats, all with the same result: -T 01/11, -T "01/11", -T 01.
>
> I pegged the severity of this bug as minor because it still tags my files
> properly despite the error.
New description:
I installed the id3v2 port and upon using it got an error like the
following for each file I processed:
id3v2(22560) malloc: *** Deallocation of a pointer not malloced:
0x90001c7a; This could be a double free(), or free() called with the
middle of an allocated block; Try setting environment variable MallocHelp
to see tools to help debug
I was initially using the id3v2 options [aAtTyg]. I narrowed the problem
down to the track number option "-T". I tried the following three
formats, all with the same result: -T 01/11, -T "01/11", -T 01.
I pegged the severity of this bug as minor because it still tags my files
properly despite the error.
--
Comment:
{{{
id3v2(22560) malloc: *** Deallocation of a pointer not malloced:
0x90001c7a; This could be a double free(), or free() called with the
middle of an allocated block; Try setting environment variable MallocHelp
to see tools to help debug
}}}
Such a message indicates a programming error which must be fixed upstream,
though I note id3v2 hasn't been updated in some time.
--
Ticket URL: <http://trac.macports.org/ticket/10027#comment:4>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list