From: Alejandro Colomar <alx@kernel.org>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: mario.blaettermann@gmail.com, linux-man@vger.kernel.org,
libc-alpha@sourceware.org
Subject: Re: Issue in man page sigaction.2
Date: Sun, 8 Feb 2026 19:11:07 +0100 [thread overview]
Message-ID: <aYjQyPt5lrAe9CuE@devuan> (raw)
In-Reply-To: <aYjJPiTfTR5I7DZL@meinfjell.helgefjelltest.de>
[-- Attachment #1: Type: text/plain, Size: 3304 bytes --]
Hi Helge,
On 2026-02-08T17:34:54+0000, Helge Kreutzmann wrote:
> Hello Alex,
> Am Thu, Dec 25, 2025 at 02:38:07PM +0100 schrieb Alejandro Colomar:
> > > Subject: Re: Issue in man page sigaction.2
> >
> > I believe the report is about sprof.2.
>
> No, probably sprof.1.
Sorry for the typo. Yes, it should be sprof.1.
>
> I rerun the example programm in sprof(1), and it works in the sense,
> that no error is reported. However, there is also no sensible output
> either, just the headers.
>
> But I don't know (I'm not a programmer) if this is a problem or just a
> normal output.
TBH, I don't know either, as I never used sprof(1).
>
> > On Wed, Dec 24, 2025 at 02:38:24PM +0000, 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!
> >
> > This has been reported in
> > <https://lore.kernel.org/linux-man/20251020093148.vve2nui3xtym4z6m@jwilk.net/>
> > and previously in
> > <https://lore.kernel.org/linux-man/ZznJf0DLo7CVHddl@meinfjell.helgefjelltest.de/>
> >
> > Please go to the thread in
> > <https://lore.kernel.org/linux-man/87mshxxyol.fsf@oldenburg.str.redhat.com/>
> > where glibc maintainers are expecting feedback from you (or whoever
> > reported to you).
>
> I was not aware that there was an open question directed to me, sorry.
> I'm not sure how to properly answer that from this e-mail, I hope it
> is sufficient that I simply CC libc-alpha@sourceware.org?
At a minimum, a reply would need the following header fields:
Cc: <libc-alpha@sourceware.org>
In-Reply-To: <87mshxxyol.fsf@oldenburg.str.redhat.com>
That should be enough. Let me know if you need more help. I've bounced
the whole thread to you so that you have it in your mailbox; that will
make it easier for you to reply.
Have a lovely night!
Alex
>
> > > "$B< sprof -p libdemo.so.1 $LD_PROFILE_OUTPUT/libdemo.so.1.profile>;\n"
> > > "Flat profile:\n"
> > > "\\&\n"
> > > "Each sample counts as 0.01 seconds.\n"
> > > " % cumulative self self total\n"
> > > " time seconds seconds calls us/call us/call name\n"
> > > " 60.00 0.06 0.06 100 600.00 consumeCpu1\n"
> > > " 40.00 0.10 0.04 1000 40.00 consumeCpu2\n"
> > > " 0.00 0.10 0.00 1 0.00 x1\n"
> > > " 0.00 0.10 0.00 1 0.00 x2\n"
>
> This looks like the following with me (Debian stable):
>
> 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
>
> Greetings
>
> Helge
>
> --
> Dr. Helge Kreutzmann debian@helgefjell.de
> Dipl.-Phys. http://www.helgefjell.de/debian.php
> 64bit GNU powered gpg signed mail preferred
> Help keep free software "libre": http://www.ffii.de/
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-02-08 18:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-24 14:38 Issue in man page sigaction.2 Helge Kreutzmann
2025-12-25 13:38 ` Alejandro Colomar
2026-02-08 17:34 ` Helge Kreutzmann
2026-02-08 18:11 ` Alejandro Colomar [this message]
2026-02-08 18:22 ` Helge Kreutzmann
-- strict thread matches above, loose matches on Subject: below --
2025-12-24 14:38 Helge Kreutzmann
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=aYjQyPt5lrAe9CuE@devuan \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.