pidgin/pidgin

Add fuzzing support for some libpurple features
release-2.x.y
2021-06-24, Jordy Zomer <>
97c51d97d375
Add fuzzing support for some libpurple features

Testing Done:
Hi!

I built and tested all of these fuzzers for libpurple.

You can build them by first building pidgin/libpurple with `--enable-fuzzing` then going into `libpurple/tests` and run `make check`. After that you can run these fuzzers. With a dictionary if you want :)

for example:
```bash
$ ./fuzz_markup_strip_html -dict=dictionaries/html.dict
Dictionary: 465 entries
INFO: Seed: 2274862685
INFO: Loaded 1 modules (3 inline 8-bit counters): 3 [0x5a4ec0, 0x5a4ec3),
INFO: Loaded 1 PC tables (3 PCs): 3 [0x568ee8,0x568f18),
INFO: -max_len is not provided; libFuzzer will not generate inputs larger than 4096 bytes
INFO: A corpus is not provided, starting from an empty corpus
#2 INITED cov: 2 ft: 2 corp: 1/1b exec/s: 0 rss: 30Mb
#1048576 pulse cov: 2 ft: 2 corp: 1/1b lim: 4096 exec/s: 524288 rss: 789Mb
#2097152 pulse cov: 2 ft: 2 corp: 1/1b lim: 4096 exec/s: 524288 rss: 792Mb
```

Best Regards,

Jordy Zomer

Reviewed at https://reviews.imfreedom.org/r/760/
/** @page xfer-signals File Transfer Signals
@signals
@signal file-recv-accept
@signal file-recv-start
@signal file-recv-cancel
@signal file-recv-complete
@signal file-recv-request
@signal file-send-accept
@signal file-send-start
@signal file-send-cancel
@signal file-send-complete
@endsignals
@see ft.h
<hr>
@signaldef file-recv-accept
@signalproto
void (*file_recv_accept)(PurpleXfer *xfer, gpointer data);
@endsignalproto
@signaldesc
Emitted when an incoming file transfer has been accepted.
@param xfer The file transfer
@param data User data
@endsignaldef
@signaldef file-recv-start
@signalproto
void (*file_recv_start)(PurpleXfer *xfer, gpointer data);
@endsignalproto
@signaldesc
Emitted when an incoming file transfer has been started.
@param xfer The file transfer
@param data User data
@endsignaldef
@signaldef file-recv-cancel
@signalproto
void (*file_recv_cancel)(PurpleXfer *xfer, gpointer data);
@endsignalproto
@signaldesc
Emitted when an incoming file transfer has been canceled.
@param xfer The file transfer
@param data User data
@endsignaldef
@signaldef file-recv-complete
@signalproto
void (*file_recv_complete)(PurpleXfer *xfer, gpointer data);
@endsignalproto
@signaldesc
Emitted when an incoming file transfer has been completed.
@param xfer The file transfer
@param data User data
@endsignaldef
@signaldef file-recv-request
@signalproto
void (*file_recv_request)(PurpleXfer *xfer, gpointer data);
@endsignalproto
@signaldesc
Emitted before the user is prompted for an incoming file-transfer.
Plugins can intercept the signal to auto-accept/auto-reject the
requests. To auto-accept the file transfer, use
purple_xfer_request_accepted(). To auto-reject, set the status of the
xfer to PURPLE_XFER_STATUS_CANCEL_LOCAL.
@param xfer The file transfer
@param data User data
@endsignaldef
@signaldef file-send-accept
@signalproto
void (*file_send_accept)(PurpleXfer *xfer, gpointer data);
@endsignalproto
@signaldesc
Emitted when an outgoing file transfer has been accepted.
@param xfer The file transfer
@param data User data
@endsignaldef
@signaldef file-send-start
@signalproto
void (*file_send_start)(PurpleXfer *xfer, gpointer data);
@endsignalproto
@signaldesc
Emitted when an outgoing file transfer has started.
@param xfer The file transfer
@param data User data
@endsignaldef
@signaldef file-send-cancel
@signalproto
void (*file_send_cancel)(PurpleXfer *xfer, gpointer data);
@endsignalproto
@signaldesc
Emitted when an outgoing file transfer has been canceled.
@param xfer The file transfer
@param data User data
@endsignaldef
@signaldef file-send-complete
@signalproto
void (*file_send_complete)(PurpleXfer *xfer, gpointer data);
@endsignalproto
@signaldesc
Emitted when an outgoing file transfer has been completed.
@param xfer The file transfer
@param data User data
@endsignaldef
*/
// vim: syntax=c.doxygen tw=75 et