libevent读书笔记

最新推荐文章于 2022-02-25 19:38:17 发布

giskook

最新推荐文章于 2022-02-25 19:38:17 发布

阅读量715

点赞数

CC 4.0 BY-SA版权

分类专栏：网络 c 文章标签： libevent c

本文链接：https://blog.youkuaiyun.com/giskook/article/details/9297967

网络 c 专栏收录该内容

1 篇文章

订阅专栏

本文介绍了libevent中自定义log和内存分配的方法，并详细解释了通过调试锁和事件使用来排查问题的具体步骤。此外，还展示了如何利用union实现内存对齐。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

1.libevent使用回调可以让用户自定义log和内存分配，回调的威力

2.libevent的替换内存分配过程中使用了一个union，赶脚很霸气

/* This union's purpose is to be as big as the largest of all the
 * types it contains. */
union alignment {
    size_t sz;
    void *ptr;
    double dbl;
};
/* We need to make sure that everything we return is on the right
   alignment to hold anything, including a double. */
#define ALIGNMENT sizeof(union alignment)

注释写的很明显了。

3.调试锁 (Debugging lock usage)

实在没有想到会有这样的方法，值得借鉴。可检测出来的问题包括：

(1)unlocking a lock that we don’t actually hold

(2)re-locking a non-recursive lock

方法：

void evthread_enable_lock_debugging(void);

#define evthread_enable_lock_debuging() evthread_enable_lock_debugging()

note ：This function MUST be called before any locks are created or used. To be safe, call it just after you set your threading functions

有意思的是这个evthread_enable_lock_debuging()在之前的版本是有个拼写错误的:P

看了看内容发现自己功力不够 :( 读不懂... ...5555555,果断跳过。

4.调试事件(Debugging event usage)

(1)Treating an uninitialized struct event as though it were initialized.

(2)Try to reinitialize a pending struct event.

由于是要花费额外的内存和cpu，所以就是为了排错才会用到专门的调试函数

void event_enable_debug_mode(void);

This function must only be called before any event_base is created.