X-Git-Url: https://git.xonotic.org/?a=blobdiff_plain;f=regression_tests%2Fq3map2%2Fsegmentation_fault%2FREADME.txt;fp=regression_tests%2Fq3map2%2Fsegmentation_fault%2FREADME.txt;h=05f30d2f5df98bfd33b28a87f29b7ba15fdf88dc;hb=a36b39a62b8e98f2cd0a767eb6f4b39350816191;hp=0000000000000000000000000000000000000000;hpb=a16ee23adf02f564d2074ebf2b5f3a839cd07167;p=xonotic%2Fnetradiant.git

diff --git a/regression_tests/q3map2/segmentation_fault/README.txt b/regression_tests/q3map2/segmentation_fault/README.txt
new file mode 100644
index 00000000..05f30d2f
--- /dev/null
+++ b/regression_tests/q3map2/segmentation_fault/README.txt
@@ -0,0 +1,27 @@
+DESCRIPTION OF PROBLEM:
+=======================
+
+The example map, maps/segmentation_fault.map, contains an example of this
+bug.  q3map2 might segfault while compiling this map.  This sort of thing
+might happen in certain intermediate versions of q3map2 while work is being
+done on fixing the math accuracy.  The bug may not have happened in older
+version of q3map2, before the math accuracy issues were addressed.
+
+To trigger the bug, compile the map; you don't need -vis or -light.  Only
+-bsp (the first q3map2 stage) is necessary to trigger the bug.  The only
+entities in the map are a light and a info_player_deathmatch, so the map will
+compile for any Q3 mod.
+
+Here is a description of the problem brush (brush #0):
+
+  side 0: -z face
+  side 1: +z face
+  side 2: -y face
+  side 3: +x face
+  side 4: +y face
+  side 5: -x face
+  side 6: problem side "accidentally showed up" :-)
+
+Side 6 is actually a superfluous plane and will be NULL'ed out in the code.
+If the code does not handle a NULL'ed out winding correctly, it will
+segfault.