Unused laps cause memory overflow.

- Forums - Sign Up - Reply - Search - Statistics -

Huidae Cho's Private Forums / libdlusb / Unused laps cause memory overflow.

Author	Message
Huidae Cho Admin	# Posted: 15 Apr 2009 00:28 - Edited by: Huidae Cho Reply Quoting: Michael I noticed another bug in the chrono code. It sets the unused laps to whatever is passed in, not accounting for the number of laps that are already used. The only check is for between 5 and 250 unused laps. So I could have 250 used laps, and the code would allow me to specify an additional 250 unused laps. The watch would then overflow, probably causing a critical runtime issue. Would you please look into this and verify that it's a problem?
Huidae Cho Admin	# Posted: 9 May 2009 10:59 - Edited by: Huidae Cho Reply Fixed in version 0.0.10. Please test it and let me know if you have any problems.
mstone Member	# Posted: 9 May 2009 21:57 Reply Thank you, Huidae! I really appreciate your working on these issues. I'll test it as soon as I get a chance.
mstone Member	# Posted: 11 May 2009 22:17 Reply This appears to be fixed, but I only tested it once. Thanks again.
Huidae Cho Admin	# Posted: 12 May 2009 04:12 Reply Please test it with 0.0.10rc2. Thanks.
mstone Member	# Posted: 13 May 2009 19:23 Reply 0.0.10rc is broken. print_chrono now outputs totally bogus data. I have 3 workouts on my watch - one from yesterday with 22 laps, one from today with 42 laps, and another from today with 5 laps. But here's what I get from print_chrono: lap_split 1 0 2005-02-00 monday 02:55:78.16 1 0 2005-02-00 monday 05:13:03.01 22 0 2005-03-16 monday 00:56:14.30 64 0 2005-03-30 monday 06:40:99.05 64 0 2005-03-30 monday 13:26:38.01 64 0 2005-03-30 monday 19:51:56.02 I noticed that you've removed the -u parameter altogether.