Ideally unexec should handle the case where heap and bss is not next
to each other, and then this workaround can be removed.
Yes, that's the task that we need for the release, for
the sake of exec-shield.
But we also need something done to deal with the randomization feature.
> "Dan" == Dan Nicolaescu <[EMAIL PROTECTED]> writes:
Dan> The problem occurs in Fedora Core 4. On a FC4 system:
Dan> echo 0 >/proc/sys/kernel/randomize_va_space is required
Dan> in order to be able to dump Emacs.
I've not had any problems dumping emacs with Linus' and Andrew's
recent kernel
Masatake YAMATO <[EMAIL PROTECTED]> writes:
>> exec_shield could be gotten around with using
>> setarch i386 make
>> and configure does that already IIRC. But the address space
>> randomization was prohibiting the dumping even with the setarch
>> command.
>>
>> It may be poss
> Masatake YAMATO <[EMAIL PROTECTED]> writes:
>
> > Sorry to be late.
> >
> > > Richard Stallman <[EMAIL PROTECTED]> writes:
> > >
> > > > What I remember is that Red Hat enables a feature in Linux that (I
> > > > believe) uses the address space differently. unexelf.c doesn't handle
Masatake YAMATO <[EMAIL PROTECTED]> writes:
> Sorry to be late.
>
> > Richard Stallman <[EMAIL PROTECTED]> writes:
> >
> > > What I remember is that Red Hat enables a feature in Linux that (I
> > > believe) uses the address space differently. unexelf.c doesn't handle
> > > it righ
Masatake YAMATO <[EMAIL PROTECTED]> writes:
Sorry to be late.
exec_shield is one such feature, and newer kernels use something
like, uh, /proc/sys/vm/randomize_... (I don't remember the
particular name right now and don't have a Fedora active). The
latter loaded executables' memory segments
Masatake YAMATO <[EMAIL PROTECTED]> writes:
> Sorry to be late.
>
>> exec_shield is one such feature, and newer kernels use something
>> like, uh, /proc/sys/vm/randomize_... (I don't remember the
>> particular name right now and don't have a Fedora active). The
>> latter loaded executables' memor
> > Richard Stallman <[EMAIL PROTECTED]> writes:
> >
> > > What I remember is that Red Hat enables a feature in Linux that (I
> > > believe) uses the address space differently. unexelf.c doesn't handle
> > > it right.
> > >
> > > I don't remember the name of the feature, but I'm sure other people
> exec_shield could be gotten around with using
> setarch i386 make
> and configure does that already IIRC. But the address space
> randomization was prohibiting the dumping even with the setarch
> command.
>
> It may be possible for unexec to get around that problem by writin
Sorry to be late.
> Richard Stallman <[EMAIL PROTECTED]> writes:
>
> > What I remember is that Red Hat enables a feature in Linux that (I
> > believe) uses the address space differently. unexelf.c doesn't handle
> > it right.
> >
> > I don't remember the name of the feature, but I'm sure other p
exec_shield could be gotten around with using
setarch i386 make
and configure does that already IIRC. But the address space
randomization was prohibiting the dumping even with the setarch
command.
It may be possible for unexec to get around that problem by writing a
suitable k
11 jun 2005 kl. 01.34 skrev David Kastrup:
Richard Stallman <[EMAIL PROTECTED]> writes:
What I remember is that Red Hat enables a feature in Linux that (I
believe) uses the address space differently. unexelf.c doesn't
handle
it right.
I don't remember the name of the feature, but I'm su
Richard Stallman <[EMAIL PROTECTED]> writes:
> What I remember is that Red Hat enables a feature in Linux that (I
> believe) uses the address space differently. unexelf.c doesn't handle
> it right.
>
> I don't remember the name of the feature, but I'm sure other people
> on this list remember the
What I remember is that Red Hat enables a feature in Linux that (I
believe) uses the address space differently. unexelf.c doesn't handle
it right.
I don't remember the name of the feature, but I'm sure other people
on this list remember the name.
___
> We need someone to fix the problem that unexelf.c has in dumping with
> some recent Linux versions used by Red Hat GNU/Linux. This is a very
> serious problem. Would someone please work on it?
How can I reproduce the problem?
Could you give me a pointer to know more?
___
15 matches
Mail list logo
