public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "sinan.lin at linux dot alibaba.com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/30693] Assertion `closure->pieces.size () == 1' failed
Date: Tue, 01 Aug 2023 03:47:27 +0000	[thread overview]
Message-ID: <bug-30693-4717-HPBWKZZpRy@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30693-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30693

--- Comment #5 from sinan <sinan.lin at linux dot alibaba.com> ---
Created attachment 15028
  --> https://sourceware.org/bugzilla/attachment.cgi?id=15028&action=edit
dwarf info of log_write_notifier

Thanks for the guide! The attachment is the dwarf info of the problematic
function, and the binary is generated through g++12.2
```
DW_AT_producer    ("GNU C++17 12.2.1 20221121 (Red Hat 12.2.1-7)
-moutline-atomics -march=armv8-a+crc -mlittle-endian -mabi=lp64 -g -g -O2 -O2
-std=c++17 -fno-omit-frame-pointer -ffp-contract=off -ftls-model=initial-exec
-fexceptions -fstack-protector-strong -fasynchronous-unwind-tables
-fstack-clash-protection -ffunction-sections -fdata-sections -fPIC
-fplugin=annobin")
```

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-08-01  3:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-28  9:06 [Bug gdb/30693] New: " sinan.lin at linux dot alibaba.com
2023-07-28 12:06 ` [Bug gdb/30693] " tromey at sourceware dot org
2023-07-29 11:03 ` sinan.lin at linux dot alibaba.com
2023-07-29 15:09 ` tromey at sourceware dot org
2023-07-30 13:53 ` simark at simark dot ca
2023-08-01  3:47 ` sinan.lin at linux dot alibaba.com [this message]
2023-08-01  3:53 ` sinan.lin at linux dot alibaba.com
2023-08-01  3:54 ` sinan.lin at linux dot alibaba.com
2023-08-01 18:08 ` tromey at sourceware dot org
2023-08-07 18:05 ` tromey at sourceware dot org

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=bug-30693-4717-HPBWKZZpRy@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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).