Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: "Ömer Sinan Ağacan" <omeragacan@gmail.com>
Cc: gdb <gdb@sourceware.org>
Subject: Re: Buildling gdb on Ubuntu 18.04
Date: Wed, 30 Jan 2019 14:58:00 -0000	[thread overview]
Message-ID: <35b21a4d59530644ce75e76fb8be8bbd@polymtl.ca> (raw)
In-Reply-To: <CAMQQO3=3C1-4GDNomZ9MtH3ccYiU+T=+zPk_p53Kt_PBhkkw=w@mail.gmail.com>

On 2019-01-30 02:40, Ömer Sinan Ağacan wrote:
> I'm trying to build gdb from git on Ubuntu 18.04 to see if some of the 
> bugs I'm
> observing with machine interface of 8.1.0.20180409-git are fixed in the
> development version. I got a few different errors before but with some 
> help from
> people on the IRC channel I was able to make progress, and current 
> status is
> this: https://gist.github.com/osa1/4548c5bc2d167541557e0a349944eb00
> 
> Does anyone have any ideas on how to move from there? Kernel version on 
> Ubuntu
> 18.04: 4.15.0-44-generic
> 
> Thanks
> 
> Ömer

About this error:

nat/gdb_ptrace.h:129:8: error: ‘PTRACE_TYPE_RET’ does not name a type; 
did you mean ‘PTRACE_TYPE_ARG3’?

The PTRACE_TYPE_RET type should be defined in the gdb/config.h file, in 
your build directory.  For example, I have

650 /* Define as the return type of ptrace. */                           
           │warning: File 
"/home/emaisin/build/binutils-gdb/gdb/gdb-gdb.py" auto-loading has be
651 #define PTRACE_TYPE_RET long


Is there a mention of PTRACE_TYPE_RET in your config.h?  I assume it is 
undefined?

Simon


  reply	other threads:[~2019-01-30 14:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-30  7:41 Ömer Sinan Ağacan
2019-01-30 14:58 ` Simon Marchi [this message]
2019-01-30 15:12   ` Ömer Sinan Ağacan
2019-01-30 15:50     ` Simon Marchi
2019-01-30 19:45       ` Ömer Sinan Ağacan
2019-01-30 20:01         ` Simon Marchi
2019-01-31  6:23           ` Ömer Sinan Ağacan
2019-01-31 15:54             ` Simon Marchi

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=35b21a4d59530644ce75e76fb8be8bbd@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=gdb@sourceware.org \
    --cc=omeragacan@gmail.com \
    /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