Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gdb: add fix for gdb 7.12 and gdb 8.0 build on noMMU platforms
Date: Thu, 10 Aug 2017 14:23:23 +0200	[thread overview]
Message-ID: <20170810142323.2ea80af0@windsurf> (raw)
In-Reply-To: <ff2def1e-0ac7-4d73-2083-f67ca110b280@mind.be>

Hello,

On Thu, 10 Aug 2017 11:25:27 +0200, Arnout Vandecappelle wrote:

> > Fixes:
> > 
> > ../nat/linux-ptrace.c: In function 'int linux_fork_to_function(gdb_byte*, int (*)(void*))':
> > ../nat/linux-ptrace.c:273:29: error: invalid conversion from 'void*' to 'gdb_byte* {aka unsigned char*}' [-fpermissive]
> >        child_stack = xmalloc (STACK_SIZE * 4);
> > 
> > The patch has already been merged upstream, as of commit
> > ffce45d2243e5f52f411e314fc4e1a69f431a81f, and will therefore be part
> > of future gdb releases.
> > 
> > Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>  
> 
>  Since this is an upstream patch, and the additional issue reported by Romain is
> something different, I applied to master, thanks.
> 
>  BTW, in another thread Thomas P. requested that a build fix which doesn't have
> an accompanying autobuild failure should have a defconfig to reproduce :-).

Right, will do next time. You should have dropped my patch, I could
have done a respin with a defconfig included in the commit log.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-08-10 12:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-03  7:15 [Buildroot] [PATCH] gdb: add fix for gdb 7.12 and gdb 8.0 build on noMMU platforms Thomas Petazzoni
2017-08-04 20:43 ` Romain Naour
2017-08-05 12:23   ` Thomas Petazzoni
2017-08-05 20:14     ` Romain Naour
2017-08-10  9:25 ` Arnout Vandecappelle
2017-08-10 12:23   ` Thomas Petazzoni [this message]
2017-09-05 21:45 ` Peter Korsgaard

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=20170810142323.2ea80af0@windsurf \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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