Valery Reznic wrote:
Now I see it. You ager going to make string in "ps" to looks good.
That's part of it, but not all of it. If the only problem was the "ps"
output, I would have lived with it. The real problem is that argv[0] is
an actual argument that some programs use.
Think of the fo
--- On Thu, 7/3/08, Shachar Shemesh <[EMAIL PROTECTED]> wrote:
> From: Shachar Shemesh <[EMAIL PROTECTED]>
> Subject: Re: Linux executable startup stack structure
> To: [EMAIL PROTECTED]
> Cc: "linux-il" , "Fakeroot NG" <[EMAIL PROTECTED]>
Valery Reznic wrote:
Actually, I can think of four or five reasons why it may
fail, but I'll
cross those bridges when I get to them.
Could you list them ?
Let's see. Off the top of my head, these are not necessarily "won't
work" problems, but obstacles to overcome:
- I need to execu
--- On Thu, 7/3/08, Shachar Shemesh <[EMAIL PROTECTED]> wrote:
> From: Shachar Shemesh <[EMAIL PROTECTED]>
> Subject: Re: Linux executable startup stack structure
> To: [EMAIL PROTECTED]
> Cc: "linux-il" , "Fakeroot NG" <[EMAIL PROTECTED]>
Valery Reznic wrote:
I think your proposed solution will work (no reason why not)
Actually, I can think of four or five reasons why it may fail, but I'll
cross those bridges when I get to them.
And if you change AT_ENTRY in the auxv you'll trick ld-linux to think
it was loaded as interprete
--- On Thu, 7/3/08, Shachar Shemesh <[EMAIL PROTECTED]> wrote:
> From: Shachar Shemesh <[EMAIL PROTECTED]>
> Subject: Re: Linux executable startup stack structure
> To: [EMAIL PROTECTED]
> Cc: "Fakeroot NG" <[EMAIL PROTECTED]>, "linux-il"
Valery Reznic wrote:
P.S. And what do you need it for (except curiosity) ?
It's going to be a somewhat long p.s. If you understood the problem I'm
trying to solve, skip ahead to area marked "proposed solution" for how
I'll be trying to solve it.
Here's a piece of trivia for you. /lib/ld-l
ENTRY:')
Regards,
Valery.
P.S. And what do you need it for (except curiosity) ?
--- On Thu, 7/3/08, Shachar Shemesh <[EMAIL PROTECTED]> wrote:
> From: Shachar Shemesh <[EMAIL PROTECTED]>
> Subject: Linux executable startup stack structure
> To: "Fakeroot NG"
Hi,
Shachar Shemesh wrote:
am looking for some documentation on the structure of the stack when
an executable starts. I know the basics - argc, then argv, then envp.
What I'm interested in is what's beyond that. I've tried googling,
reading the sources in the kernel for fs/binfmt_elf.c and
Hi all. Sorry for the crosspost.
I am looking for some documentation on the structure of the stack when
an executable starts. I know the basics - argc, then argv, then envp.
What I'm interested in is what's beyond that. I've tried googling,
reading the sources in the kernel for fs/binfmt_elf.c
10 matches
Mail list logo
