The trouble is that the compiler is for some reason copying the argument
into a local stack slot and passing the address of that instead for &argc.
That faults because it happens to be the edge of the stack. In the case
where there is an argc word on the stack (i.e. when run by the kernel), it
pr
On Tue, Jan 08, 2002 at 01:02:26AM +0100, Marcus Brinkmann wrote:
> BTW, the corresponding glibc-2.2.4/gcc2.95 code for the above code (function
> in function) is
>
> _hurd_stack_setup:
> pushl %ebp
> movl %esp,%ebp
> subl $24,%esp
> leal 8(%ebp),%eax
> mov
On Mon, Jan 07, 2002 at 10:51:40PM +0100, Marcus Brinkmann wrote:
> 0x8048494 <_hurd_stack_setup>: push %ebp
> 0x8048495 <_hurd_stack_setup+1>:mov%esp,%ebp
> 0x8048497 <_hurd_stack_setup+3>:push %ebx
> 0x8048498 <_hurd_stack_setup+4>:sub$0x24,%esp
> 0x804849b <
Hi,
libio enabled glibc, gcc 3.0, static binaries die in _hurd_stack_setup at
start up time. I think the code is gcc generated, probably for the vararg.
Here is the relevant debug info. I am not too familiar with that code gcc
generates for what type of function invocation etc. Maybe the vara
