How to set an .EXE stack segment same as the code segment? (Developers)
> Now, I wanted to explicitly set the stack as a segment, but I can't seem to
> get WarpLink to put the stack into the same segment as the code segment. I
> tried naming a group (as "dgroup") and including both the RXCMD segment and
> the STACK$$ segment into that, and also tried setting the "class=" of the
> stack segment to RXCMD (same as the code segments), but alas. In the NASM
> source text, I need to specify the "stack" attribute to the "segment"
> instruction, which tells the linker that this is the stack segment.
>
> Anyone got any ideas?
My compiler's linker supports small-memory .EXEs with up to 64KB code segment and fixed-size 64KB data/stack segment (DS=SS, CS!=SS). The stack size option controls the location of the __start_stack__ symbol giving the heap the remainder of the segment: __start_stack__ - __stop_alldata__.
But if you're comfortable with your NASM-only solution, you probably don't need this.
Complete thread:
- How to set an .EXE stack segment same as the code segment? - ecm, 09.03.2018, 13:11
![Open in board view [Board]](img/board_d.gif)
![Open in mix view [Mix]](img/mix_d.gif)
- How to set an .EXE stack segment same as the code segment? - ecm, 09.03.2018, 14:13
- How to set an .EXE stack segment same as the code segment? - alexfru, 10.03.2018, 06:35
Mix view