brew protocol problem

I've managed to reproduce a problem reported by 8100 bitpim users when the
brew directory has too many files in.
It is due to too many directories in the filesystem, files themselves are
not a problem

This is a protocol trace of bitpim obtaining the contents of the brew
directory:

14:18:07.311 LG-VX8100: brew request Data - 8 bytes
<#! p_brew.listdirectoriesrequest !#>
00000000 59 02 05 62 72 65 77 00                             Y..brew.

14:18:07.391 LG-VX8100: brew response Data - 263 bytes
<#! p_brew.listdirectoriesresponse !#>
00000000 59 02 00 1a 00 fc 00 62 72 65 77 2f 31 30 35 31
Y......brew/1051
00000010 32 00 62 72 65 77 2f 31 31 37 39 37 00 62 72 65
2.brew/11797.bre
00000020 77 2f 31 32 34 31 34 00 62 72 65 77 2f 31 32 35
w/12414.brew/125
00000030 31 33 00 62 72 65 77 2f 31 33 31 33 36 00 62 72
13.brew/13136.br
00000040 65 77 2f 31 33 34 37 38 00 62 72 65 77 2f 31 33
ew/13478.brew/13
00000050 39 32 31 00 62 72 65 77 2f 31 33 39 32 32 00 62
921.brew/13922.b
00000060 72 65 77 2f 31 36 34 35 32 00 62 72 65 77 2f 31
rew/16452.brew/1
00000070 36 34 35 34 00 62 72 65 77 2f 31 38 31 36 39 00
6454.brew/18169.
00000080 62 72 65 77 2f 33 33 31 34 00 62 72 65 77 2f 33
brew/3314.brew/3
00000090 35 35 32 00 62 72 65 77 2f 33 36 38 32 00 62 72
552.brew/3682.br
000000a0 65 77 2f 33 39 35 39 00 62 72 65 77 2f 33 39 36
ew/3959.brew/396
000000b0 36 00 62 72 65 77 2f 34 39 37 32 00 62 72 65 77
6.brew/4972.brew
000000c0 2f 35 36 39 31 00 62 72 65 77 2f 38 34 35 31 00
/5691.brew/8451.
000000d0 62 72 65 77 2f 38 38 33 36 00 62 72 65 77 2f 39
brew/8836.brew/9
000000e0 36 33 39 00 62 72 65 77 2f 64 6f 77 6e 6c 6f 61
639.brew/downloa
000000f0 64 00 62 72 65 77 2f 65 6e 00 62 72 65 77 2f 65
d.brew/en.brew/e
00000100 73 00 00 72 65 00 00                                s..re..

The response looks ok, the number of directories is 0x1A according to the
response, but the actual number of directories listed in the packet is 2
less. Obviously the packet has overflowed. Bitpim ignores the packet length
0xFC and also read the spurious characters "re" at the end of the packets as
a directory. This results in either a crash or directories with garbage
names listed, trying to list the contents of these directoris results in a
crash.

The directories were created by downloading loads of apps (free demos).

Has anyone seen this behavior before? Does anyone know what happens with
other brew phones when the number of directory is too long to list in a
single packet.


Simon



-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. 
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php