[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] Calling GEM from within a signal handler

To: Andreas Schwab <schwab@issan.cs.uni-dortmund.de>
Subject: Re: [MiNT] Calling GEM from within a signal handler
From: Konrad Kokoszkiewicz <draco@mi.com.pl>
Date: Wed, 21 Apr 1999 16:12:30 +0200 (EEST)
Cc: Thomas Binder <gryf@hrzpub.tu-darmstadt.de>, MiNT mailing list <mint@fishpool.com>
In-reply-to: <vyzk8v9uhkp.fsf@issan.cs.uni-dortmund.de>
Sender: owner-mint@fishpool.com

> The kernel must copy the *whole* heap.  And without any non-constant data
> your program is completely useless (it can't have any stack!).

And where is the place i wrote "no constant data"? And how's the DATA
segment in your humble opinion related to presence or absence of stack?

--
Konrad M.Kokoszkiewicz
|mail: draco@mi.com.pl                  | Atari Falcon030/TT030/65XE |
|http://www.obta.uw.edu.pl/~draco/
|http://draco.atari.org

** Ea natura multitudinis est,
** aut servit humiliter, aut superbe dominatur (Liv. XXIV,25)
*************************************************************
** U pospolstwa normalne jest, ze albo sluzy ono unizenie,
** albo bezczelnie sie panoszy.

Follow-Ups:
- Re: [MiNT] Calling GEM from within a signal handler
  - From: Andreas Schwab <schwab@issan.cs.uni-dortmund.de>

References:
- Re: [MiNT] Calling GEM from within a signal handler
  - From: Andreas Schwab <schwab@issan.cs.uni-dortmund.de>

Prev by Date: [MiNT] Ext2.XFS
Next by Date: Re: [MiNT] 030-only binaries
Previous by thread: Re: [MiNT] Calling GEM from within a signal handler
Next by thread: Re: [MiNT] Calling GEM from within a signal handler
Index(es):
- Date
- Thread