glibc detected ; memory corruption

pingu · 10-10-2005, 02:06 AM

Trying to run MainActor3.7 in Mepis/Debian sarge, I get this message (started from shell):

Code:

# /opt/MainActor/maseq &
*** glibc detected *** malloc(): memory corruption: 0x########
SIGABRT
#

What does this mean:
1) Wrong version of glibc
2) Faulty memory chip
3) Something else?

teval · 10-10-2005, 09:34 PM

Most likely not a faulty version of glibc (your system wouldn't run properly). Possibly a version of glibc that's too new for it.

Possibly it just has a bug.

MainActor 3.7 is very old, try updating to version 5.5

pingu · 10-11-2005, 01:50 AM

Thing is, I tried MainActor 5.5 but I don't like it.
In 3.7 everything is easy to use, it's very intuitive. In 5.5 nothing is intuitive, I get my things done at last - but every new thing is complicated to find out, and even when I know how to do it it requires more job to get it done. I'm not going to buy 5.5, I'm so disappointed with it.

And the open-source editing tools (Kino, Avidemux, Kdenlive) doesn't let me manipulate audio or add text fields to the movie.
Now 3.7 works with LormaLinx (based on FC3), so I could do the editing there. Only Kino doesn't work with Lorma so I have to record the movies with Mepis...

If there's no way to get it working? I don't know if that error message is that important, now I found out that it pops up every now and then in LormaLinux as well? Always when I quit MainActor, but sometimes with MA running - and it doesn't die. (Only message isn't 'malloc()' but like 'free: invalid pointer' (2-3 different messages))
What is malloc() ?

pingu · 10-12-2005, 01:29 AM

Interresting...
Enabling TwinView in LormaLinux and MainActor doesn't start - same message as in Mepis.
Dissabling TwinView in Mepis doesn't help, however???

CivCTP also has problems with newer version of glibc, there is a way to compile an older version of glibc somewhere and point CivCTP to it, maybe I should try with MA as well??