public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
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: Tue, 10 Feb 2026 07:09:50 +0100	[thread overview]
Message-ID: <lhuseb9m8nl.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <aYob8JOv64u7tVtt@meinfjell.helgefjelltest.de> (Helge Kreutzmann's message of "Mon, 9 Feb 2026 17:40:00 +0000")

* Helge Kreutzmann:

> Hello Florian,
> On Mon, Feb 09, 2026 at 07:22:09AM +0100, Florian Weimer wrote:
>> > Am Sun, Nov 17, 2024 at 11:50:18PM +0100 schrieb Florian Weimer:
>> >> * Alejandro Colomar:
>  
>> > 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?
>  
> I simply copied the instructions in the man page one by one and
> observed the output, without really understanding what I'm doing. So
> yes, the problem may be perfectly on my side, that I should have
> generated some events.

The instructions work for me on Fedora 43.  It's possible that they
depend on compiler/linker default settings not being overriden by the
distribution.  Fedora only changes fewer upstream defaults than other
distributions.

Thanks,
Florian


  reply	other threads:[~2026-02-10  6:09 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
2026-02-09 17:40         ` Helge Kreutzmann
2026-02-10  6:09           ` Florian Weimer [this message]
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=lhuseb9m8nl.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