On Thursday, August 1, 2002, at 01:09 PM, Auke Nauta wrote:
> > So there actually seems to be a conflict involving lcms and > pictureopendialog. When the opendialog is skipped, the problems are > gone. This is very unlikely (technically possible) but I bet my lunch that you have some other problem. The bug will probably fall into one of the most common catagories: index off the end of an array, using an uninitialized pointer, violating the rules of the memory allocator (calling free() twice for the same pointer etc) I know nothing of Borland so specific advice is tricky - I have debugged a lot of code though. First read all your code, if you have a handy friend (victim) around run through it with them and describe how it all works - this will lead you to *many* bugs. Then, if you haven't already become familiar with your debugger. Find out how to discover the values of variables and memory contents. Then step through every line of code you every write and watch what it does. This you will find, also uncovers many errors, almost as good as explaining you code to a friend. Ok that doesn't work, next see if you can step into the lcms code in the debugger. If you can't it might be that you need to turn on "debugging info" or something similar when you build lcms. This procedure varies wildly from system to system so I can't be of any help here. Step through the lcms code until you find out the offending line there. This may lead you to clues about what is causing the crash. Code that work sometimes is the hardest to figure out. :-( Good luck! ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Lcms-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/lcms-user
