• 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.

Archived

This topic is now archived and is closed to further replies.

chrisbk

DLL + FILE * = ?

5 posts in this topic

Hi all, I have a problem with my DLL . let me explain it : In the .exe code I have the following : FILE *in = fopen(...); btm->load(in); Where btm is an object created by the DLL (this also mean that the ''load'' function is located inside the DLL). In the load function I have something that looks like : void load(in) { char header[2]; fread(header,2,1,in); .. } And this crash (Access violation) on the fread. (in != null) It also crash if I do fseek/fclose/whatever. I really don''t know what is happening (and that''s annoying me..) Anyone knows what cause this crash ? thks chris
0

Share this post


Link to post
Share on other sites
quote:
Original post by chrisbk

Hi all,

I have a problem with my DLL . let me explain it :

In the .exe code I have the following :

FILE *in = fopen(...);
btm->load(in);

Where btm is an object created by the DLL (this also mean that the ''load'' function is located inside the DLL).

In the load function I have something that looks like :


void load(in)
{
char header[2];
fread(header,2,1,in);
..
}


And this crash (Access violation) on the fread. (in != null)
It also crash if I do fseek/fclose/whatever.

I really don''t know what is happening (and that''s annoying me..)
Anyone knows what cause this crash ?


thks


chris






Try this just for fun, instead of fread(header,2,1,in), replace it with fread(&header, 2, 1, in); If I remember correctly, it''s been a long while since I used fread, that should solve your problem...




"And that''s the bottom line cause I said so!"

Cyberdrek
Headhunter Soft
A division of DLC Multimedia

Resist Windows XP''s Invasive Production Activation Technology!
0

Share this post


Link to post
Share on other sites
quote:

You would be passing a pointer to a pointer by doing &header.



Actually not, though it might seem so. In C++ (perhaps in C too, don't know) the following holds: If 'foobar' is declared as a statically allocated array, then (foobar == &foobar) is true.

Edited by - Dactylos on June 18, 2001 9:37:03 PM
0

Share this post


Link to post
Share on other sites
I can see that you tweaked your parameters a bit. Just as test, change:

fread(header,2,1,in);

--- to -----

fread(header,1,2,in);


Now that I know that having an item 2 bytes long and reading once is the same as having an item 1 byte long and reading twice, but who knows how fread is working internally. Just try it.
0

Share this post


Link to post
Share on other sites
If there isn''t a parameter problem, then the next most (very) likely thing is that the DLL was built with a different version of the C runtime library to the .exe...


If you build the .exe with the "Debug Multithreaded DLL" version of the C runtime library and you build your DLL with the "Single Threaded, static lib" version, then the handle from one will be invalid with the other... Even different versions of the same CRT can cause that.

...you get the same problem with memory allocation - if you allocate something in the DLL and try to release it in the .exe (assuming you''d DLL with different CRT to EXE), you''d get a crash.


Solutions ?:

1. Don''t try to share CRT handles/resources out of a DLL - its an unsafe programming practice - better is to wrap a version of the fopen call inside the DLL, so any handle used in the DLL is always using the same CRT.

2. If you must do it, ensure the DLL has exactly the same CRT as the EXE - setting both to use one of the CRT DLLs is the best option (eg. both should use "Single Threaded DLL"

3. The alternative is not to use the CRT, instead use Windows functions (CreateFile, ReadFile, CloseHandle etc) in both DLL and .exe, and pass HANDLEs between DLL and EXE rather than FILE*s

--
Simon O''''Connor
Creative Asylum Ltd
www.creative-asylum.com
0

Share this post


Link to post
Share on other sites