Whoever did the new FormDocument, I BLAME YOU!
I've been chasing the last hour or two (after being up all night) chasing
a bug that was supposedly in my code, after chasing it off with the unkind
help of ddd/gdb I found the culprit to be (supposedly, havent verified it
completely) in the function CloseAllBufferRelatedDialogs(), I KNOW that
the problem is in this function, what I believe is that the problem is
caused by an access to an uninitialized variable, fd_form_document and its
relatives there are a good chance.
This is not my code and I'm sleepy by now, so I'll leave it to whomever
touched one of those dialogs and didn't finish it in that function.
May I say that hunting for a bug caused by a function call that goes
through signals is a real nightmare (luckily I'm going to sleep during the
day :-), It's been a hectic hunting to find the called function. But maybe
it's because I hardly know ddd/gdb debugging methods.
For such things a debugging code in the signalling methods could be
usefull, to print the called functions before calling them. Will simplify
finding where the trouble really occured.
I'm off to sleep, good night/day/whatever.
--
Baruch Even
http://techst02.technion.ac.il/~sbaruch/ (My Site)
http://rpghost.com/jindor/ (My brothers AD&D site)
" Learn to laugh ... it's the path to true love! "
- The Angel in the movie Michael
