public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "caiyinyu at loongson dot cn" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/30258] New: sprof cannot read and display shared object profiling data correctly
Date: Tue, 21 Mar 2023 15:00:05 +0000	[thread overview]
Message-ID: <bug-30258-131@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 30258
           Summary: sprof cannot read and display shared object profiling
                    data correctly
           Product: glibc
           Version: 2.37
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: dynamic-link
          Assignee: unassigned at sourceware dot org
          Reporter: caiyinyu at loongson dot cn
  Target Milestone: ---

According to examples in
https://manpages.ubuntu.com/manpages/xenial/man1/sprof.1.html, sprof cannot
read and display shared object profiling data correctly.

The attachment is the example.

untar attachment and run:
./build.sh
./run.sh

and you will get error message:

Inconsistency detected by ld.so: dl-open.c: 930: _dl_open: Assertion
`_dl_debug_update (args.nsid)->r_state == RT_CONSISTENT' failed!

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

             reply	other threads:[~2023-03-21 15:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-21 15:00 caiyinyu at loongson dot cn [this message]
2023-03-21 15:02 ` [Bug dynamic-link/30258] " caiyinyu at loongson dot cn
2023-03-21 15:06 ` caiyinyu at loongson dot cn
2023-05-09 12:38 ` schwab@linux-m68k.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-30258-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).