http://bugs.kde.org/show_bug.cgi?id=98444
Steve VanDeBogart vandebo-valgrind nerdbox net changed:
What|Removed |Added
CC||[EMAIL PROTECTED]
This patch cleans up an usused variable in ptrace.c.
Compile tested.
Karol Swietlicki
Signed-off-by: Karol Swietlicki <[EMAIL PROTECTED]>
---
--- linux-2.6.27-rc1-mm1.orig/arch/um/kernel/ptrace.c 2008-08-27
19:20:13.0 +0200
+++ linux-2.6.27-rc1-mm1/arch/um/kernel/ptrace.c2008-08
On Wed, Aug 27, 2008 at 04:05:24PM +0100, Graham Cobb wrote:
> However, how would I go about bisecting through the large number of patches
> which are the difference between these? Is there somewhere I can get interim
> kernel versions from?
Set up a git tree, and git-bisect will chose versions
On Wed, Aug 27, 2008 at 12:34:08PM +0300, Ilpo Järvinen wrote:
> They usually say that you might want to put the return on a different line
> unless you have something to hide :-).
Whoops, right you are.
Jeff
--
Work email - jdike at linux dot intel dot com
-
On Wed, Aug 27, 2008 at 09:04:29AM +0100, Graham Cobb wrote:
> On Tuesday 26 August 2008 21:20:12 Jeff Dike wrote:
> > A symbol clash between libc and the kernel. Try this:
> >...
>
> The patch itself didn't apply for me (probably because I copy/paste'd it from
> the email) but making the chang
On Tue, Aug 26, 2008 at 08:51:51PM +0200, Stanislav Meduna wrote:
>> You can work around this by putting a 0 into /proc/sys/vm/mmap_min_addr.
>
> Permission denied here - looks quite hard readonly on this kernel
> even for root.
Hmmm. The actual fix is below,
Jeff
--
W
On Tuesday 26 August 2008 21:20:12 Jeff Dike wrote:
> A symbol clash between libc and the kernel. Try this:
>...
The patch itself didn't apply for me (probably because I copy/paste'd it from
the email) but making the change by hand to the Makefile worked and fixed the
problem.
---
On Tue, 26 Aug 2008, Jeff Dike wrote:
> On Tue, Aug 19, 2008 at 09:09:16AM +0300, Ilpo Järvinen wrote:
> > ...I'm not fully sure what's the intention here, ie., whether
> > the return belongs to a block with the assignment or not.
>
> Yes, this is confused, although it just happens to compile to
