public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: Dodji Seketeli <dodji@seketeli.org>
To: "paolo.pisati at canonical dot com" <sourceware-bugzilla@sourceware.org>
Cc: libabigail@sourceware.org
Subject: Re: [Bug default/31045] assert violation while setting translation unit for unique types
Date: Thu, 09 Nov 2023 10:06:40 +0100	[thread overview]
Message-ID: <87wmurthwf.fsf@seketeli.org> (raw)
In-Reply-To: <bug-31045-9487-3oDzs5oN9g@http.sourceware.org/bugzilla/> (paolo pisati at canonical dot com's message of "Thu, 09 Nov 2023 08:53:43 +0000")

"paolo.pisati at canonical dot com" <sourceware-bugzilla@sourceware.org>
a écrit:

> --- Comment #3 from Paolo Pisati <paolo.pisati at canonical dot com> ---
> fresh checkout of your PR31045, doesn't build:

[...]

> ../../src/abg-ir.cc: In function ‘void
> abigail::ir::maybe_set_translation_unit(const decl_base_sptr&,
> translation_unit*)’:
> ../../src/abg-ir.cc:8002:5: error: ‘member’ was not declared in this scope
>  8002 |     member->set_translation_unit(tu);

Ooops, indeed.  Could you try again please?  I have just fixed that.
Sorry for the inconvenience.


-- 
		Dodji

  reply	other threads:[~2023-11-09  9:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-08 12:03 [Bug default/31045] New: libabigail-2.4: Assertion `__abg_cond__' failed. Aborted (core dumped) paolo.pisati at canonical dot com
2023-11-08 12:04 ` [Bug default/31045] " paolo.pisati at canonical dot com
2023-11-08 14:52 ` [Bug default/31045] assert violation while setting translation unit for unique types dodji at redhat dot com
2023-11-09  8:53 ` paolo.pisati at canonical dot com
2023-11-09  9:06   ` Dodji Seketeli [this message]
2023-11-09  9:06 ` dodji at seketeli dot org
2023-11-09 12:10 ` paolo.pisati at canonical dot com
2023-11-09 12:30 ` dodji at redhat dot com

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=87wmurthwf.fsf@seketeli.org \
    --to=dodji@seketeli.org \
    --cc=libabigail@sourceware.org \
    --cc=sourceware-bugzilla@sourceware.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).