linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Neuling <mikey@neuling.org>
To: Philippe De Muyter <phdm@macqel.be>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: 3.9-rc1 powerpc ptrace.c: 'brk.len' is used uninitialized
Date: Thu, 07 Mar 2013 09:09:48 +1100	[thread overview]
Message-ID: <21084.1362607788@ale.ozlabs.ibm.com> (raw)
In-Reply-To: <20130306060058.GA3106@frolo.macqel>

> bisect tells me that since your commit 9422de3e953d0e60eb95f5430a9dd803eec1c6d7 
> "powerpc: Hardware breakpoints rewrite to handle non DABR breakpoint registers",
> compiling linux fails with :
> 
>   cc1: warnings being treated as errors
>   arch/powerpc/kernel/ptrace.c: In function 'arch_ptrace':
>   arch/powerpc/kernel/ptrace.c:1450: warning: 'brk.len' is used uninitialized in this function
>   arch/powerpc/kernel/ptrace.c:1352: note: 'brk.len' was declared here
> 
> could you look at that ?

Sure. 

How are you compiling this?  Is there a ppc defconfig that hits it?

Mikey

  reply	other threads:[~2013-03-06 22:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-06  6:00 3.9-rc1 powerpc ptrace.c: 'brk.len' is used uninitialized Philippe De Muyter
2013-03-06 22:09 ` Michael Neuling [this message]
2013-03-06 22:36   ` Philippe De Muyter
2013-03-06 23:14     ` Michael Neuling
2013-03-07  9:59       ` Philippe De Muyter
2013-03-07 22:32         ` Michael Neuling
2013-03-07 23:03           ` Michael Neuling
2013-03-08 10:24             ` Philippe De Muyter
2013-03-12  2:42               ` powerpc/ptrace: Fix brk.len used uninitialised Michael Neuling

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=21084.1362607788@ale.ozlabs.ibm.com \
    --to=mikey@neuling.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=phdm@macqel.be \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).