RefPtr: Clarify comment about undefined behaviour

Dereferencing a null pointer does not necessarily cause a segfault:
it is undefined behaviour, which means anything, or nothing, may happen.
Avoid setting an expectation that a segfault will reliably occur here.

1 files changed, 1 insertions, 1 deletions

diff --git a/glib/glibmm/refptr.h b/glib/glibmm/refptr.h
index 892b6a67..a5970783 100644
--- a/glib/glibmm/refptr.h
+++ b/glib/glibmm/refptr.h
@@ -88,7 +88,7 @@ private:
 public:
   /** Default constructor
    *
-   * Afterwards it will be null and use of -> will cause a segmentation fault.
+   * Afterwards it will be null and use of -> will invoke undefined behaviour.
    */
   inline RefPtr() noexcept;