public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Luis Machado <luis.machado@arm.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org, jose.marchesi@oracle.com, vapier@gentoo.org
Subject: Re: GDB 12.0.90 available for testing
Date: Wed, 13 Apr 2022 08:36:05 +0100	[thread overview]
Message-ID: <c20304ba-7fc9-db12-5555-d413350852fd@arm.com> (raw)
In-Reply-To: <YlW9o1IAKJ/CRk8c@adacore.com>

Hi Joel,

On 4/12/22 18:57, Joel Brobecker wrote:
> Hi Luis,
> 
>> On 3/20/22 05:58, Joel Brobecker via Gdb-patches wrote:
>>> Hello,
>>>
>>> I have just finished creating the gdb-12.0.90 pre-release.
>>> It is available for download at the following location:
>>>
>>>       ftp://sourceware.org/pub/gdb/snapshots/branch/gdb-12.0.90.tar.xz
>>>
>>> A gzip'ed version is also available: gdb-12.0.90.tar.gz.
>>>
>>> Please give it a test if you can and report any problems you might find.
>>>
>>> On behalf of all the GDB contributors, thank you!
>>
>> It seems GDB doesn't build with --enable-targets=all for 32-bit Arm. I think
>> this is a long-standing bug that has not been fixed yet.
>>
>> I'd consider this a blocker for the release, as builds shouldn't fail.
> 
> Generally speaking, I tend to agree, but at the same time, it really
> depends.
> 
> Is this specific to GDB 12, or did we have this issue with previous
> releases?

This has been introduced in GDB 12 development as far as I remember. It 
is similar/related to the following:

https://sourceware.org/pipermail/binutils/2021-November/118485.html

Also discussed slightly in 
https://sourceware.org/bugzilla/show_bug.cgi?id=28684.

I reported it back then: 
https://sourceware.org/pipermail/binutils/2021-November/118554.html.

It might be an easy configure adjustment, but I'm not familiar with bpf.

I know Jose Marchesi did work on bpf, but I'm not sure if he is the 
right PoC.

> 
> We also need some kind of visibility as to how quickly we think we can
> solve that issue. This usually requires someone to act as the issue's
> "champion" -- that person might not be the one actually making the fix,
> but they can at least try help expedite the process.

Agreed. I just want to make sure this has visibility so we can try to 
fix it before release.

> 
>> I get the following:
>>
>> binutils-gdb-armhf-bionic/sim/bpf/../../../../repos/binutils-gdb/sim/bpf/../common/sim-close.c:43:
>> undefined reference to `bpf_cgen_cpu_close'
>>
>> binutils-gdb-armhf-bionic/sim/bpf/../../../../repos/binutils-gdb/sim/bpf/sim-if.c:166:
>> undefined reference to `bpf_cgen_cpu_open_1'
>>
>> binutils-gdb-armhf-bionic/sim/bpf/../../../../repos/binutils-gdb/sim/bpf/sim-if.c:179:
>> undefined reference to `bpf_cgen_init_dis'
>>
>> This is GCC 7.5.0 on Ubuntu 18.04.
>>
>> Should I go ahead and open a ticket against the release? I'm not sure who is
>> responsible for handling BPF.
> 
> I'd start by asking Mike Frysinger, who's the sim maintainer.
> He might not know about this particular target, but he's made
> a lot of cleanups in this area.
> 
> In this case, hopefully the fix won't be too difficult.
> 

cc-ed both Mike and Jose Marchesi.

Thanks,
Luis

  reply	other threads:[~2022-04-13  7:36 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-20  5:58 Joel Brobecker
2022-03-26 15:26 ` Eli Zaretskii
2022-03-26 15:53   ` Joel Brobecker
2022-03-26 16:15     ` Eli Zaretskii
2022-04-07 16:08       ` Tom Tromey
2022-04-07 16:12         ` Eli Zaretskii
2022-04-07 18:00           ` Joel Brobecker
2022-04-07 18:04             ` Simon Marchi
2022-04-07 19:02             ` Tom Tromey
2022-04-07 19:11               ` Joel Brobecker
2022-04-08 13:38                 ` Tom Tromey
2022-04-08 14:33                   ` Pedro Alves
2022-04-18 15:26                     ` Tom Tromey
2022-04-18 16:13                       ` Tom Tromey
2022-04-07 18:30           ` Tom Tromey
2022-04-08  6:58             ` Eli Zaretskii
2022-04-18 19:28               ` Tom Tromey
2022-03-26 17:59 ` Eli Zaretskii
2022-03-26 18:34   ` Eli Zaretskii
2022-03-26 18:51     ` Eli Zaretskii
2022-03-27  6:27       ` Eli Zaretskii
2022-03-31  6:23         ` Eli Zaretskii
2022-03-31  9:48           ` Pedro Alves
2022-03-31 11:55             ` Eli Zaretskii
2022-04-01 10:12               ` Andrew Burgess
2022-04-01 11:18                 ` Eli Zaretskii
2022-04-01 11:25                   ` Eli Zaretskii
2022-04-01 15:21                     ` Andrew Burgess
2022-04-01 16:18                       ` Eli Zaretskii
2022-04-03 13:02                         ` Hannes Domani
2022-04-03 13:34                           ` Eli Zaretskii
2022-04-03 14:03                           ` Joel Brobecker
2022-04-03 15:26                             ` Hannes Domani
2022-04-03 15:38                               ` Eli Zaretskii
2022-04-07 11:09                                 ` Eli Zaretskii
2022-04-07 18:03                                   ` Joel Brobecker
2022-04-10 19:06                                     ` Joel Brobecker
2022-04-11 11:42                                       ` Eli Zaretskii
2022-04-17 17:28                                         ` Joel Brobecker
2022-04-19 16:12                                           ` Andrew Burgess
2022-04-19 16:16                                             ` Eli Zaretskii
2022-04-20 13:26                                               ` Andrew Burgess
2022-04-20 17:11                                               ` Joel Brobecker
2022-04-20 17:30                                                 ` Eli Zaretskii
2022-04-24 15:56                                             ` Joel Brobecker
2022-04-25  8:48                                               ` Andrew Burgess
2022-04-07 18:28                                   ` Tom Tromey
2022-04-07 19:22                                   ` Pedro Alves
2022-04-08  4:04                                     ` Eli Zaretskii
2022-04-01 12:36                   ` Joel Brobecker
2022-04-01 12:50                     ` Eli Zaretskii
2022-04-01 14:12                       ` Joel Brobecker
2022-04-01 14:27                         ` Eli Zaretskii
2022-04-01 14:31                           ` Joel Brobecker
2022-04-08 14:44                             ` Pedro Alves
2022-04-08 20:05                               ` Eli Zaretskii
2022-03-27  9:55     ` Eli Zaretskii
2022-03-27  1:55   ` Simon Marchi
2022-03-27  5:20     ` Eli Zaretskii
2022-04-07 16:13       ` Tom Tromey
2022-04-07 16:39         ` Eli Zaretskii
2022-03-31  6:21   ` Eli Zaretskii
2022-03-31  9:44     ` Pedro Alves
2022-03-31 11:58       ` Eli Zaretskii
2022-03-31 12:05         ` Pedro Alves
2022-03-31 14:00           ` Eli Zaretskii
2022-04-12 14:01 ` Luis Machado
2022-04-12 17:57   ` Joel Brobecker
2022-04-13  7:36     ` Luis Machado [this message]
2022-04-13 12:19       ` Luis Machado
2022-04-13 16:20         ` Jose E. Marchesi
2022-04-17 17:33           ` Joel Brobecker
2022-04-18  1:48             ` Alan Modra
2022-04-26 13:54             ` Luis Machado
2022-04-26 14:56               ` Joel Brobecker
2022-04-26 15:15                 ` Luis Machado
2022-04-20 17:33 ` Pedro Alves
2022-04-20 17:52   ` Joel Brobecker

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=c20304ba-7fc9-db12-5555-d413350852fd@arm.com \
    --to=luis.machado@arm.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jose.marchesi@oracle.com \
    --cc=vapier@gentoo.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).