-
Notifications
You must be signed in to change notification settings - Fork 4
/
Copy pathBUGS
33 lines (23 loc) · 1.15 KB
/
BUGS
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
===============================================================================
What to do if you find a bug
===============================================================================
In the hopefully rare circumstance that you find a bug, please report it to me
by e-mail: <paul@lucasmail.org>. Please include the following information:
1. A description of the problem.
2. Operating system and version.
3. Compiler used and version.
4. The exact command line used.
5. If the program dumps core (C++) or throws an exception (Java), a stack trace.
-------------------------------------------------------------------------------
To get a stack trace for C++:
1. A "core" file should be generated (if the filesystem is writable and you
have write permission to it). For macOS, core files are placed in the
directory /cores and are of the form core.XXXXX where XXXXX is the process
ID.
If you can write to the filesystem yet no core file was generated, type:
ulimit -c unlimited
and try again.
2. Execute gdb by typing:
gdb /path/to/chsm-executable /path/to/core
3. Then in gdb, type "where" and copy and paste the output into an e-mail to
me.