Re: __stack_start for ColdFire uClinux
Larry Baker <[email protected]>
| Newsgroups | gmane.linux.uclinux.devel |
|---|---|
| Message-ID | <[email protected]> |
Greg, On 3 Oct 2012, at 3:06 PM, Larry Baker wrote: > In the mean time, I'll try using _end instead of __stack_start for the stack limit symbol. gcc -fstack-limit-symbol=_end works. > I don't know the ld scripting language. I will try to figure out how to define __start_stack to have the same value as, for example, .bss _end. Here's a patch that corrects the definition of __stack_start in elf2flt.ld.in: --- elf2flt-orig/elf2flt.ld.in +++ elf2flt/elf2flt.ld.in @@ -172,3 +172,3 @@ @SYMBOL_PREFIX@_stack_start = .; - } + } > flatmem With the patch, gcc -fstack-limit-symbol=__stack_start works. Please have the people that maintain elf2flt take a look at it. That is, the stack check trips and the program exits without clobbering the stack. It is silent, though -- there is no indication that SIGILL occurred. I still haven't figured out how to enable a message and/or register dump when this happens. Larry Baker US Geological Survey 650-329-5608 [email protected] _______________________________________________ uClinux-dev mailing list [email protected] http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by [email protected] To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev