mldonkey, a multi-networks file-sharing client - Bugs: bug #9197, Exception...
You are not allowed to post comments on this tracker with your current authentication level.
bug #9197: Exception Invalid_argument("out-of-bound array or string access") on certain searches
| Submitter: | None | ||
| Submitted: | Wed 02 Jun 2004 09:31:43 PM UTC | ||
| Category: | HTTP interface | Severity: | 3 - Normal |
| Item Group: | Program malfunction | Status: | Fixed |
| Assigned to: | None | Open/Closed: | Closed |
| Release: | 2-5-21 | Release: | |
| Operating System: | Linux | Binaries Origin: | CVS / Self compiled |
| CPU type: | Intel x86 | ||
|
Thu 19 May 2005 02:09:18 PM UTC, comment #5: |
spiralvoice <spiralvoice> |
|
Tue 12 Apr 2005 06:00:29 PM UTC, comment #4: please tell us (or me in private if you prefer) on exactly what searches. |
Amorphous <amorphous> |
|
Tue 12 Apr 2005 10:05:39 AM UTC, comment #3: Please check if this bug still is in current CVS version.
|
spiralvoice <spiralvoice> |
|
Tue 01 Feb 2005 07:41:03 PM UTC, comment #2: Please try version 2-5-28p_bt and report if the bug still exists. |
spiralvoice <spiralvoice> |
|
Sun 06 Jun 2004 12:56:24 PM UTC, comment #1: Are there non-ASCII characters in these search results? |
spiralvoice <spiralvoice> |
|
Wed 02 Jun 2004 09:31:43 PM UTC, original submission:
Both the telnet and HTTP interface give me:
|
Anonymous |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 4 latest changes.
| Date | Changed by | Updated Field | Previous Value | => | Replaced by |
|---|---|---|---|---|---|
| 2005-05-19 | spiralvoice | Status | Need Info | Fixed | |
| Open/Closed | Open | Closed | |||
| 2005-04-12 | amorphous | Status | None | Need Info | |
| 2005-03-16 | amorphous | Item Group | Compilation problem | Program malfunction |

Because of the many UTF-8 changes I consider this bug solved,
mainly because in bug #9102:
"However, from 2.5.30, UTF-8 also seems to return good result."