• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
Arppa

glibc: munmap_chunk(): invalid pointer

9 posts in this topic

I'm working on a SDL+GL project and I encountered a following error and I can't figure out what's the problem. Code: Uint8* key = NULL; key = SDL_GetKeyState(NULL); // Error occures here if (key[SDLK_0]) // handle key ... and throws a following error *** glibc detected *** /home/arppa/projs/debrislinux/bin/Debug/debrislinux: munmap_chunk(): invalid pointer: 0x0816cdf8 *** + backtrace + memory map i'm using sdl version 1.2.12 Has someone seen this error before and knows what's wrong. I'm pretty sure it's not the code becouse it runs fine on windows. Thanks in advance.
0

Share this post


Link to post
Share on other sites
Make your program with -O0 -ggdb -g3 flags (and if you have gcc with SSP extension, -fstack-protector-all). If program still fails, run it in debugger (on linux, i recommend gdb), and look on backtrace.
0

Share this post


Link to post
Share on other sites
There's no way that that piece of code causes that error, unless SDL_GetKeyState has a bug in it, which is very unlikely. What's happening is that you are corrupting the heap somewhere else in your program and this is where it happens to manifest. Use Valgrind to track down where you are trashing memory.
0

Share this post


Link to post
Share on other sites
I tried compiling with -O0 -ggdb -g3 -fstack-protector-all but with no success.
I've used exactly this same code on windows but I'm now compiling the code on linux and getting that error. When I comment out: key = SDL_GetKeyState(NULL); everything works, no errors, but also no key states :( . Of course I could just boot back to windows, but I'm curious what causes that error. I'm using glibc version 2.7
0

Share this post


Link to post
Share on other sites
Quote:
Original post by Arppa
I tried compiling with -O0 -ggdb -g3 -fstack-protector-all but with no success.
I've used exactly this same code on windows but I'm now compiling the code on linux and getting that error. When I comment out: key = SDL_GetKeyState(NULL); everything works, no errors, but also no key states :( . Of course I could just boot back to windows, but I'm curious what causes that error. I'm using glibc version 2.7


Valgrind will tell you where the problem is instantly.
0

Share this post


Link to post
Share on other sites
I tried Valgrind and for what I understand the output it seems not to be my coding error.
Full output: http://pastebin.com/m4895d6ec
0

Share this post


Link to post
Share on other sites
Quote:
Original post by Arppa
I tried Valgrind and for what I understand the output it seems not to be my coding error.
Full output: http://pastebin.com/m4895d6ec


The first two entries might be issues with the system libraries. They're potential security problems, but we'll ignore them for now.


==20273== Invalid write of size 4
==20273== at 0x804B4AA: dSystem::dInputManager::LoadIdentityKeySet() (dInputManager.cpp:309)
==20273== by 0x804C43B: dSystem::dInputManager::dInputManager() (dInputManager.cpp:16)
==20273== by 0x805202F: main (main.cpp:73)
==20273== Address 0x65a4fdc is 4 bytes after a block of size 304 alloc'd
==20273== at 0x4021F14: operator new[](unsigned) (in /usr/lib/valgrind/x86-linux/vgpreload_memcheck.so)
==20273== by 0x804C3ED: dSystem::dInputManager::dInputManager() (dInputManager.cpp:8)
==20273== by 0x805202F: main (main.cpp:73)


This means you are allocating some memory at line 8 of dInputManager.cpp (in the dInputManager constructor), and later you are writing 4 bytes past the end of the chunk of memory. This overwrite happens in dInputManager.cpp at line 309. This is a real heap corruption bug and might be the cause of your problem.

The others are all saying that you're using memory that has not be initialized with a known value. For example, look at the code in dMath.cpp at line 23. You're passing a value to sqrt which has not been initialized (i.e. it contains random data). You need to look through your code to work out how this could happen and fix it up.

Also, you didn't paste the full log or it got truncated by the pastebin. I can't see the entries where Valgrind ends and reports any memory leaks, which also means I might not be seeing any other errors it reported that could be causing your problem.
0

Share this post


Link to post
Share on other sites
That fixed the problem. I've to say that Valgrind is a quite good tool. Many thanks to you!
0

Share this post


Link to post
Share on other sites
Hi guys, I have this error, too.

My situation is much more strange. I created a window with some widgets using gtkmm. I also rewrite MFC's CArray for use in Linux. I found that the constructor of CArray is automatically called several times although I didn't declare any CArray in the main function. I even empty the main() function and remove all includes, like this:

int main() { return 0; }

and then run the program. It still throws out the munchunk() glibc error after calling several times the CArray constructor. Really strange, as the body of the main is empty!!!

I guess there's a problem with those linking libraries of gtkmm?

I'm using Eclipse on Ubuntu in joint with gtkmm library for my project.

Any hints? Thanks in advance.
0

Share this post


Link to post
Share on other sites
Phew, finally know what the reason is.

Actually I did allocate some elements in the array like T* elements = new T[size] and then only use "delete elements" in the destructor. This will leave some trash elements remaining in the heap so some further operations (which?, who knows!) will throw errors. I changed to "delete[] elements" to ensure every objects in the array is deleted properly and the error is gone.

Just wonder why those error is so terrible to figure out? (glibc throws exception although I didn't touch it)

And many thanks to the Valgrind tool since I would not have know the bug without it. :)
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0