On 02/03/2023 09:22, Francois-Xavier Le Bail wrote:
> On 01/03/2023 20:28, Denis Ovsienko wrote:
>> On Tue, 28 Feb 2023 17:01:51 +0100
>> Francois-Xavier Le Bail <devel.fx.leb...@orange.fr> wrote:
>>
>>> In addition to printf()/fprintf(), here is a brand new way to help
>>> debugging a program using libpcap, currently only tested on Debian
>>> Linux (stable).
>>>
>>> (Similar method to the one available with tcpdump and tcpslice.)
>>>
>>> The goal is to generate instrumentation calls for entry and exit to
>>> functions. Just after function entry and just before function exit,
>>> the profiling functions are called and print the function names with
>>> indentation and call level. If entering in a function, print also the
>>> calling function name with file name and line number. There may be a
>>> small shift in the line number.
>>>
>>> To use it:
>>> (There will be a doc entry based on this topic later.)
>>
>> Thank you for putting this together.  Does the FAQ look the best place
>> for such documentation?
> 
> The documentation could be added to the FAQ indeed.

The documentation has been added:
https://www.tcpdump.org/faq.html#q17


_______________________________________________
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

Reply via email to