The Ur-Quan Masters Home Page Welcome, Guest. Please login or register.
Did you miss your activation email?
January 28, 2020, 09:07:46 pm
Home Help Search Login Register
News: Paul & Fred have reached a settlement with Stardock!

+  The Ur-Quan Masters Discussion Forum
|-+  The Ur-Quan Masters Re-Release
| |-+  Technical Issues (Moderator: Death 999)
| | |-+  [Linux] malloc(): memory corruption error
« previous next »
Pages: [1] Print
Author Topic: [Linux] malloc(): memory corruption error  (Read 4103 times)
GekkoGeck0
Zebranky food
*
Offline Offline

Gender: Female
Posts: 11



View Profile
[Linux] malloc(): memory corruption error
« on: April 09, 2006, 12:44:57 am »

I'm having problems running UQM 0.5.0.

My system is:
AMD Duron 1.1GHz
256MB RAM
NVidia GeForce 2 MMX
Kernel version is 2.6.12-12mdk

Here's what I get when I run UQM:

Set the resolution to: 640x480x32
Screen scalers are using SSE/MMX-Ext/MMX code
*** glibc detected *** malloc(): memory corruption (fast): 0x083db9b8 ***
Aborted

Does anyone know why this is happening? I'm totally stumped.
Logged
Novus
Enlightened
*****
Offline Offline

Gender: Male
Posts: 1938


Fot or not?


View Profile
Re: [Linux] malloc(): memory corruption error
« Reply #1 on: April 09, 2006, 04:20:27 am »

Weird. Sounds like some part of UQM is overwriting malloc's data structures; a typical case of writing outside allocated blocks. However, I haven't seen UQM do this before.

Have you compiled this yourself, or is this a precompiled binary? Have you tried the CVS version of UQM?

Either way, it looks like a bug in UQM (or, theoretically, SDL). I suggest you file a bug report.
Logged

RTFM = Read the fine manual.
RTTFAQ = Read the Ur-Quan Masters Technical FAQ.
meep-eep
Forum Admin
Enlightened
*****
Offline Offline

Posts: 2847



View Profile
Re: [Linux] malloc(): memory corruption error
« Reply #2 on: April 09, 2006, 01:52:48 am »

Did you compile UQM yourself? Or was this a binary package? In the latter case, from which distribution?
If you compiled it yourself, does this occur in debug mode, or only in release mode?
It would be useful if you could include a core file in the bug report (if you don't get a core file, do "ulimit -c unlimited" in bash or zsh, or "limit coredumpsize unlimited" in tcsh), as well as the binary that goes with it.
A debug mode core file and executable are much more usable for us, so if you've compiled it yourself, and the problem occurs in debug mode, please send us those.
Also it may be useful for us to know what version of glibc and SDL you're running on your system.
Logged

“When Juffo-Wup is complete
when at last there is no Void, no Non
when the Creators return
then we can finally rest.”
GekkoGeck0
Zebranky food
*
Offline Offline

Gender: Female
Posts: 11



View Profile
Re: [Linux] malloc(): memory corruption error
« Reply #3 on: April 09, 2006, 08:40:37 am »

It was compiled myself, on Mandriva 2006. It occurs in release mode. I have not tried the CVS version.

glibc-2.3.5-5mdk
libSDL1.2-1.2.8

I am not familiar with core files...

Perhaps if I recompile the program in debug mode?

Logged
meep-eep
Forum Admin
Enlightened
*****
Offline Offline

Posts: 2847



View Profile
Re: [Linux] malloc(): memory corruption error
« Reply #4 on: April 09, 2006, 05:21:12 pm »

A core file is a dump of the process state at the time of the crash (or abort() call in this case).
If you have creation of core files on (which is what the command lines I mentioned were to do), a core file will be created in the current directory at the time of a crash.
If the same problem occurs in debug mode, it will contain more useful information to help us track down the problem.
Logged

“When Juffo-Wup is complete
when at last there is no Void, no Non
when the Creators return
then we can finally rest.”
Pages: [1] Print 
« previous next »
Jump to:  


Login with username, password and session length

Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!