Bug#547678: memory corruption on long filename

2010-01-02 Thread Elimar Riesebieter
* fa...@gmx.de [100102 13:42 +0100] > On Sat, Jan 02, 2010 at 01:22:15PM +0100, Elimar Riesebieter wrote: > > > Does this behaviour still exists for you?. I can't reproduce it > > either with blanks nor apostrophes nor both. There might be a > > problem with the ID tag of your file, but this I can

Bug#547678: memory corruption on long filename

2010-01-02 Thread Elimar Riesebieter
* fa...@gmx.de [090924 01:32 +0200] [...] > After the corruption error I run: killall -9 mocp > That should kill all instances, right? > (If I don't do that, another instance would hang, waiting for the crashed > server to respond.) > > > > Else it could help at the moment to clos > > all mocp in

Bug#547678: memory corruption on long filename

2009-09-23 Thread fagga
On Thu, Sep 24, 2009 at 01:10:53AM +0200, Elimar Riesebieter wrote: > * fa...@gmx.de [090923 23:39 +0200] > > On Wed, Sep 23, 2009 at 11:27:25PM +0200, Elimar Riesebieter wrote: > > > * fa...@gmx.de [090923 23:17 +0200] > > > > > I can't reproduce with a wc -m 164 character counted file. Even on >

Bug#547678: memory corruption on long filename

2009-09-23 Thread Elimar Riesebieter
* fa...@gmx.de [090923 23:39 +0200] > On Wed, Sep 23, 2009 at 11:27:25PM +0200, Elimar Riesebieter wrote: > > * fa...@gmx.de [090923 23:17 +0200] > > > > I can't reproduce with a wc -m 164 character counted file. Even on > > > > 32bit nor on 64bit. Maybe you have to fiddle a bit with ulimit. > > >

Bug#547678: memory corruption on long filename

2009-09-23 Thread Elimar Riesebieter
* fa...@gmx.de [090923 23:17 +0200] > > I can't reproduce with a wc -m 164 character counted file. Even on > > 32bit nor on 64bit. Maybe you have to fiddle a bit with ulimit. > > bash(1) search for ulimit. > > Core dumps seem to be disabled in the Debian kernel (why?), and I currently > don't have

Bug#547678: memory corruption on long filename

2009-09-23 Thread fagga
On Wed, Sep 23, 2009 at 11:27:25PM +0200, Elimar Riesebieter wrote: > * fa...@gmx.de [090923 23:17 +0200] > > > I can't reproduce with a wc -m 164 character counted file. Even on > > > 32bit nor on 64bit. Maybe you have to fiddle a bit with ulimit. > > > bash(1) search for ulimit. > > > > Core dum

Bug#547678: memory corruption on long filename

2009-09-23 Thread fagga
> I can't reproduce with a wc -m 164 character counted file. Even on > 32bit nor on 64bit. Maybe you have to fiddle a bit with ulimit. > bash(1) search for ulimit. Core dumps seem to be disabled in the Debian kernel (why?), and I currently don't have time to find out how to recompile and install a

Bug#547678: memory corruption on long filename

2009-09-23 Thread Elimar Riesebieter
tag 547678 unreproducible thanks * Benjamin [090921 15:32 +0200] > Package: moc > Version: 1:2.5.0~alpha3+svn20090611-1+b1 > Severity: normal > > When I try to play a file with a quite long filename (156 characters), I get > this error message: > ** glibc detected *** mocp: malloc(): memory corru

Bug#547678: memory corruption on long filename

2009-09-22 Thread Damian Pietras
On Mon, Sep 21, 2009 at 03:32:20PM +0200, Benjamin wrote: > Package: moc > Version: 1:2.5.0~alpha3+svn20090611-1+b1 > Severity: normal > > When I try to play a file with a quite long filename (156 characters), I get > this error message: > ** glibc detected *** mocp: malloc(): memory corruption: 0

Bug#547678: memory corruption on long filename

2009-09-21 Thread Elimar Riesebieter
forwarded 547678 da...@daper.net thanks * Benjamin [090921 15:32 +0200] > Package: moc > Version: 1:2.5.0~alpha3+svn20090611-1+b1 > Severity: normal > > When I try to play a file with a quite long filename (156 characters), I get > this error message: > ** glibc detected *** mocp: malloc(): memor

Bug#547678: memory corruption on long filename

2009-09-21 Thread Benjamin
Package: moc Version: 1:2.5.0~alpha3+svn20090611-1+b1 Severity: normal When I try to play a file with a quite long filename (156 characters), I get this error message: ** glibc detected *** mocp: malloc(): memory corruption: 0x09b2a290 *** Renaming the file resolves the issue. -- System Informa