| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Secondary thread / Guard-page excep |
Hello Mike!
Replying to a message of Mike Bilow to Erik Huelsmann:
EH>> I did not install an exception handler for this secondary
EH>> thread, but the compiler's runtime-library does not seem to
EH>> install one for the main thread and does not seem to have
EH>> any problems in stack-expansion....
[some stuff deleted]
EH>> PS: I did try to run the thread using the Commit-stack
EH>> option. This does the trick, but I don't want to be placed
EH>> back into the 16-bit age where I need to try to determine
EH>> the max. size my stack will grow to.
MB> It is not the job of the operating system to allocate your memory for
MB> you, but only to gracefully notify you of the need to do so. This is
MB> done for a very good reason. There are a number of algorithms used
MB> to try to minimize thrashing of the stack allocator,
Sure, but I have an OS/2-bookcollection CD here, and as I conclude from the
control-program reference guide (description of the DosXXX-api calls):
there is a system default behavior for all exceptions know to OS/2 (not
application-defined exceptions). So there must be a predefined behavior for
guard-page-exceptions. This default behavior should (in my opinion) then be
the commitment of extra stack-pages.
MB> the simplest and
MB> most common being to double the stack size on each exception.
MB> However, all such algorithms have some cases in which they will enter
MB> pathological breakdown, and the choice of the right algorithm is far
MB> from simple.
Ok, I agree with that. Deep down I was hoping not to have to write my own
exception-handler, since I know how to program, but only on the
application-side, not the OS-side. (I don't want to need to program this
side...) But if there is no other answer to that, then it will have to be
done.
Can you advise me some good document on exception-handling (ie.
programming) and guard-page/access-violation exceptions?
Bye, Erik!
[TeamOS/2 NL]
preferred personal reactions through e-mail
[internet: ErikH{at}hcc-gron.idn.nl]
--- FleetStreet 1.14 NR
* Origin: ORIGINal messages, I like them (2:500/19.1929)SEEN-BY: 50/99 78/0 270/101 620/243 711/401 409 410 413 430 808 809 934 955 SEEN-BY: 712/407 515 517 628 713/888 800/1 7877/2809 @PATH: 500/19 9 28/777 2/777 396/1 270/101 712/515 711/808 809 934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.