File: BUGS

package info (click to toggle)
swish++ 6.1.5-2
  • links: PTS
  • area: main
  • in suites: squeeze
  • size: 2,256 kB
  • ctags: 1,759
  • sloc: ansic: 11,931; lisp: 804; sh: 629; perl: 366; makefile: 80
file content (41 lines) | stat: -rw-r--r-- 1,273 bytes parent folder | download | duplicates (7)
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
34
35
36
37
38
39
40
41
===============================================================================
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: <pauljlucas@mac.com>.  Please include the following information:

1. A description of the problem.
2. Operating system and version.
3. The exact command line used.
4. If the command dumps core, a stack trace.

To get a stack trace:

1. Go to the "config" directory and edit the "config.mk" file uncommenting the
   line:

	DEBUG:=		true

2. Go back to the top-level directory and type:

	make distclean
	make

3. Re-execute the same command to make it dump core again.  A "core" file
   should be generated (if the filesystem is writable and you have write
   permission to it).  For Mac OS X, 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.

4. Execute gdb by typing:

	gdb /path/to/swish++-executable /path/to/core

5. Then in gdb, type "where" and copy and paste the output into an e-mail
   message to me.