]>
Commit | Line | Data |
---|---|---|
8356cc1d | 1 | ############################################################################### |
2 | # This file contains the list of bugs (features) found in this software. # | |
3 | # Any new problems should be appended to this file with a new sequential # | |
4 | # number and current date and time, for example the output of the date # | |
5 | # command. # | |
6 | # Hopefully at some point these will be fixed at which point the bug listing # | |
7 | # can be removed from this file. Please check carefully that the problem has # | |
8 | # infact been resolved before you remove the bug listing. Rather add a tag of # | |
9 | # RESOLVED to the bug heading for a while before removing the bug if you are # | |
10 | # not sure. # | |
11 | ############################################################################### | |
12 | =============================================================================== | |
13 | ||
14 | 1) Wed Nov 24 21:30:19 SAST 2004 | |
15 | ||
16 | Strange segfault with triggerDDL when running: | |
17 | > ./bin/Linux-debug/triggerDDL list <x> | |
18 | where <x> is in the range 1 to 1023 we get a SegFault. | |
19 | For <x> larger than 1023 the program runs normally. | |
20 | ||
21 | list is a file containing the line: | |
22 | "file" | |
23 | and file is a empty file. | |
24 | ||
25 | =============================================================================== | |
26 | ||
27 | 2) Wed Nov 24 21:30:19 SAST 2004 | |
28 | ||
29 | Assertion failure in triggerDDL when running | |
30 | > ./bin/Linux-debug/triggerDDL list | |
31 | ||
32 | Message: | |
33 | triggerDDL: /home/artur/HLT/dHLT/src/new.cpp:144: void operator delete [](void*): Assertion `checkmem.RemoveArrayAlloc(memory)' failed. | |
34 | ||
35 | list is a file containing the line: | |
36 | "file" | |
37 | and file is a empty file. | |
38 | ||
39 | =============================================================================== | |
40 | ||
41 | 3) Wed Nov 24 22:30:35 SAST 2004 | |
42 | ||
43 | Data packets in BCMP::Receiver can be received multiple times. We need to fix | |
44 | this by adding code that checks if the packet was already received or not. | |
45 | Could use some kind of windowing algorithm like TCP uses. | |
46 | ||
47 | =============================================================================== | |
48 |