Did you change the code associated with the short and long file names? =20=
The crash is in the code looking for the short name and I remember you =20=
wanted to get rid of them.... If you didn't then I have a new version =20=
that checks a return value (which it should have before) and prevents a =20=
crash.
brian
On May 16, 2005, at 5:21 PM, Jaime Chang wrote:
> I was testing usbkey with one FAT16 partition that contained active =20=
> and deleted directories and files.
>
> I run the fls command against the FAT16 partition and it segmented =20
> fault
>
> + r/r 73217: D3X100K.txt
> + r/r 73218: D3Y1M-E.txt
> d/d * 5: _IR004
> d/d 6: =20
> =
OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO=20=
> OOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
> Segmentation fault (core dumped)
>
> gdb output:
>
> #0 0x08063af5 in fatfs_dent_parse_block (fatfs=3D0x807e048, =20
> buf=3D0x807f038 "=E5IR002 \020", len=3D512, addr=3D384, flags=3D7, =
=20
> fs_dent=3D0x8084068,
> action=3D0x8070335 <print_dent_act>, ptr=3D0x0) at fatfs_dent.c:464
>
> I can see that buf address has junk in it (buf=3D0x807f038 "=E5IR002 =
=20
> \020")
|