From: Florian Weimer <fweimer@redhat.com>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: Alejandro Colomar <alx@kernel.org>,
mario.blaettermann@gmail.com, linux-man@vger.kernel.org,
libc-alpha@sourceware.org
Subject: Re: Issue in man page sprof.1
Date: Mon, 09 Feb 2026 07:22:09 +0100 [thread overview]
Message-ID: <lhuqzquv3la.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <aYjV0n96GmH-lZl-@meinfjell.helgefjelltest.de> (Helge Kreutzmann's message of "Sun, 8 Feb 2026 18:28:34 +0000")
* Helge Kreutzmann:
> Hello Florian,
> Am Sun, Nov 17, 2024 at 11:50:18PM +0100 schrieb Florian Weimer:
>> * Alejandro Colomar:
>>
>> > Hi Helge,
>> >
>> > On Sun, Nov 17, 2024 at 10:46:23AM GMT, Helge Kreutzmann wrote:
>> >> Without further ado, the following was found:
>> >>
>> >> Issue: Inconsistency detected by ld.so: dl-open.c: 930: _dl_open: Assertion `_dl_debug_update (args.nsid)->r_state == RT_CONSISTENT' failed!
>> >
>> > IIUC, this report is that running the example shell session resulted in
>> > that problem. I've CCed glibc in case they can help.
>> >
>> > It would be interesting to know if this can be reproduced, and a full
>> > reproducer.
>>
>> Hasn't this been fixed in glibc 2.38? Via:
>>
>> commit ab5aa2ee3d3f978e474803cbbc5fe805ad30e293
>> Author: Andreas Schwab <schwab@suse.de>
>> Date: Thu Mar 23 16:46:20 2023 +0100
>>
>> dlopen: skip debugger notification for DSO loaded from sprof (bug 30258)
>>
>> Avoid inconsistent state in the debugger interface.
>
> Apologies that I missed that question.
>
> In Debian stable (Trixie), glibc 2.41-12+deb13u1, this error is no
> longer present.
I think we should then assume that your issue was bug 30258.
> I can run all commands of sprof(1), however none produces any content,
> i.e. something beyond the header lines. As I'm not a programmer, I
> don't know if this is something to worry about.
>
> helge@twentytwo:/tmp$ sprof -p libdemo.so.1 $LD_PROFILE_OUTPUT/libdemo.so.1.profile
> Flat profile:
>
> Each sample counts as 0,01 seconds.
> % cumulative self self total
> time seconds seconds calls us/call us/call name
Is it possible that no profiling events have been recorded?
How do you call functions in libdemo.so.1?
Thanks,
Florian
next prev parent reply other threads:[~2026-02-09 6:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-17 10:46 Issue in man page sprof.1 Helge Kreutzmann
2024-11-17 11:55 ` Alejandro Colomar
2024-11-17 22:50 ` Florian Weimer
2026-02-08 18:28 ` Helge Kreutzmann
2026-02-09 6:22 ` Florian Weimer [this message]
2026-02-09 17:40 ` Helge Kreutzmann
2026-02-10 6:09 ` Florian Weimer
2024-11-19 13:29 ` Carlos O'Donell
2024-11-19 16:18 ` Helge Kreutzmann
2024-11-20 22:04 ` Carlos O'Donell
-- strict thread matches above, loose matches on Subject: below --
2025-08-24 14:48 Helge Kreutzmann
2025-09-01 13:43 ` Alejandro Colomar
2025-09-01 16:25 ` Helge Kreutzmann
2025-10-19 15:07 ` Helge Kreutzmann
2025-10-20 9:31 ` Jakub Wilk
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=lhuqzquv3la.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=alx@kernel.org \
--cc=debian@helgefjell.de \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
--cc=mario.blaettermann@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