Mail Archives: djgpp/2002/01/10/09:27:58
--- Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:
> It is something you should worry about. Whether you
> need to change
> the code or work around the problem somehow can only
> be decided after
> analyzing the code and understanding the problems.
>
> In general, code that uses the DS/SS/ES registers in
> an interrupt
> handler is unsafe because the DJGPP data segment
> might be invalid
> when there's a signal pending. The __djgpp_ds_alias
> variable is
> provided for that reason: it always has a value of a
> valid selector
> which spans the same memory as what DS usually does.
Mmmm...
I'll check some things out, and see what I can find...
> Then post the full text of the message here, and
> someone will help
> you with the debugger.
Well, here it is...
The instruction at "0x0f00115e" referenced memory at
"0xffffffff". The memory could not be "read".
After that, I can press OK or CANCEL, where OK quits
and CANCEL starts Visual C++ 6.0 for debugging.
I also tried debugging with GDB, but something went
wrong there... I've never worked with GDB before, so
it could be my fault, but when the program crashed,
GDB crashed too!
> Bothe Ctrl-C and the alarm signal work the same way
> in DJGPP: they
> both invalidate the DS selector. So I think you
> should take a good
> look at the PMCOM's interrupt handler, to see
> whether it uses the DS
> selector, or references some variable on the stack.
I'll take a look into it, and see if I can find
anything...
__________________________________________________
Do You Yahoo!?
Send FREE video emails in Yahoo! Mail!
http://promo.yahoo.com/videomail/
- Raw text -