1berry/wireshark
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix broken links to developer-old.gnome.org

Browse Source 
Replace with current https://docs.gtk.org links

Fixes #20415
This commit is contained in:
Michael Mann 2025-05-28 21:56:17 -04:00
parent 9f75b9e06b
commit 9379cfbfdf
4 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/wsdg_src/wsdg_sources.adoc
View File

@ -509,7 +509,7 @@ $ export WIRESHARK_DEBUG_WMEM_OVERRIDE=simple
Wireshark uses GLib's GSlice memory allocator, either indirectly via wmem or via various GLib API calls.
GLib provides a `G_SLICE` environment variable that can be set to `always-malloc` (similar to `simple`) or `debug-blocks` (similar to `strict`).
See https://developer-old.gnome.org/glib/stable/glib-running.html for details.
See https://docs.gtk.org/glib/running.html for details.
The C libraries on FreeBSD, Linux, and macOS also support memory allocation debugging via various environment variables.
You can enable many of them by running `source tools/debug-alloc.env` in a POSIX shell.

4
doc/wsug_src/wsug_io.adoc
View File

@ -501,7 +501,7 @@ I 2019-05-14T19:04:57Z
==== Regular Text Dumps
Wireshark is also capable of scanning the input using a custom Perl regular
expression as specified by GLib's https://developer-old.gnome.org/glib/stable/glib-regex-syntax.html[GRegex here].
expression as specified by GLib's https://docs.gtk.org/glib/struct.Regex.html[GRegex here].
Using a regex capturing a single packet in the given file
Wireshark will search the given file from start to the second to last character
(the last character has to be `\n` and is ignored)
@ -628,7 +628,7 @@ Packet format regular expression::
This is the regex used for searching packets and metadata inside the input file.
Named capturing subgroups are used to find the individual fields. Anchors `^` and
`$` are set to match directly before and after newlines `\n` or `\r\n`. See
https://developer-old.gnome.org/glib/stable/glib-regex-syntax.html[GRegex] for a full
https://docs.gtk.org/glib/struct.Regex.html[GRegex] for a full
documentation.
Data encoding::

2
epan/maxmind_db.c
View File

@ -55,7 +55,7 @@ static char mmdbr_stop_sentinel[] = "\x04"; // ASCII EOT. Could be anything.
// The GLib documentation says that g_rw_lock_reader_lock can be called
// recursively:
// https://developer-old.gnome.org/glib/stable/glib-Threads.html#g-rw-lock-reader-lock
// https://docs.gtk.org/glib/method.RWLock.reader_lock.html
// However, g_rw_lock_reader_lock calls AcquireSRWLockShared
// https://gitlab.gnome.org/GNOME/glib/blob/master/glib/gthread-win32.c#L206
// and SRW locks "cannot be acquired recursively"

2
wsutil/wmem/wmem_map.h
View File

@ -41,7 +41,7 @@ typedef struct _wmem_map_t wmem_map_t;
* the map is fully destroyed. Items stored in it will not be freed unless they
* were allocated from the same scope. For details on the GHashFunc and
* GEqualFunc parameters, see the glib documentation at:
* https://developer-old.gnome.org/glib/stable/glib-Hash-Tables.html
* https://docs.gtk.org/glib/struct.HashTable.html
*
* If the keys are coming from untrusted data, do *not* use glib's default hash
* functions for strings, int64s or doubles. Wmem provides stronger equivalents