https://bugzilla.novell.com/show_bug.cgi?id=661750
https://bugzilla.novell.com/show_bug.cgi?id=661750#c0 Summary: Setting value of hexadecimal NumericUpDown control to 0 crashes Mono runtime Classification: Mono Product: Mono: Class Libraries Version: 2.8.x Platform: x86 OS/Version: All Status: NEW Severity: Normal Priority: P5 - None Component: Windows.Forms AssignedTo: [email protected] ReportedBy: [email protected] QAContact: [email protected] Found By: Corporate Interoperability Test Blocker: --- Created an attachment (id=406526) --> (http://bugzilla.novell.com/attachment.cgi?id=406526) Test application to demonstrate the bug. Description of Problem: If the value of a NumericUpDown control in hexadecimal mode is set to 0 the application (runtime) stops working (without a stack trace). Steps to reproduce the problem: 1. Compile and run the attached code. 2. Press the button (which sets the value to 0) - or - Write 0 into the text box and press enter - or - Press the decrementer Actual Results: On Windows (Mono 2.8.x) and Ubuntu (Mono 2.6.x) the application stops working and has to be terminated. Expected Results: 0 is an allowed value for the control (verfied with .NET runtime). How often does this happen? Always. Additional Information: The bug only occurs if the control is in hexadecimal mode. The problem seems to be located in NumericUpDown::UpdateEditText() as after the member 'Text' is already set to "0" because num_chars is 0 the expression is further evaluated which results in 'Text' is set to an empty string. This empty string is also the side effect if the initial value of the control is 0. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
