Issue 7846 - Program crashes when user tries to enter 0 to column size textbox in the "Insert Table" dialogue box.
Summary: Program crashes when user tries to enter 0 to column size textbox in the "Ins...
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 1.0.1
Hardware: PC Windows ME
: P3 Trivial (vote)
Target Milestone: ---
Assignee: Oliver Specht
QA Contact: issues@sw
URL:
Keywords: oooqa
: 7874 9655 9658 9685 (view as issue list)
Depends on:
Blocks:
 
Reported: 2002-09-23 19:31 UTC by Unknown
Modified: 2003-09-08 16:56 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Dr. Watson log from crash (20.84 KB, text/plain)
2002-09-23 23:26 UTC, prgmgr 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2002-09-23 19:31:42 UTC 
Reduplication Steps:
1. Create a new text document in OO 1.0.1
2. Click the insert table icon on the "Insert" floating bar. This opens an 
insert table dialogue box.
3. Clear default value 5, and then enter 0 from keyboard to column size text 
box.
4. Move cursor away, 0 is automatically changed to 1.
5. Move cursor to column size text box again, and try to clear 1.
6. A warning message pops up. "An unrecoverable error has occurred. All 
modified files have been saved and probably be recovered at program start."
7. Press OK. A second warning message pops up.  "Soffice has caused an error in 
SWE641MI.DLL. Soffice will now close. If you continue to experience problems, 
try restarting your computer. Close? Debug?"

I reproduced this bug on both Win Me/ OO1.0.1 and Win 2000/ OO1.0.1. On Win 
2000/OO 1.0.1, the second warning message is about division by zero. "The 
exception Integer division by zero. (0x0000094) occurred in the application at 
location 0x1e479ed8. OK? Cancel?". "The instruction at "0x00000001" reference 
memory at "0x00000001". The memory could not be "read" OK? Cancel?".
Comment 1 prgmgr 2002-09-23 23:25:29 UTC 
Jiehua, thanks for posting this issue.

Duplicated on Win NT 4.0 SP6a, OOo 1.0.1.
Comment 2 prgmgr 2002-09-23 23:26:26 UTC 
Created attachment 2948 [details]
Dr. Watson log from crash
Comment 3 Oliver Specht 2002-09-24 07:37:18 UTC 
Stack: 
SW643MI! SwInsTableDlg::ModifyRowCol(class NumericField *) + 40 bytes
SW643MI! SwInsTableDlg::LinkStubModifyRowCol(void *,void *) + 14 bytes
VCL643MI! Edit::Modify(void) + 145 bytes
VCL643MI! NumericField::Modify(void) + 25 bytes
VCL643MI! Edit::Modify(void) + 66 bytes
VCL643MI! Edit::ImplModified(void) + 42 bytes
VCL643MI! Edit::ImplHandleKeyEvent(class KeyEvent const &) + 2518 bytes
VCL643MI! Edit::KeyInput(class KeyEvent const &) + 31 bytes
VCL643MI! ImplWindowFrameProc(void *,class SalFrame *,unsigned
short,void const *) + 2909 bytes
Comment 4 Oliver Specht 2002-09-24 07:45:07 UTC 
fixed in sw/source/ui/table/instable.cxx in SRX644d
Comment 5 Oliver Specht 2002-09-25 07:40:46 UTC 
*** Issue 7874 has been marked as a duplicate of this issue. ***
Comment 6 Oliver Specht 2002-11-29 07:58:50 UTC 
*** Issue 9655 has been marked as a duplicate of this issue. ***
Comment 7 Oliver Specht 2002-11-29 08:00:26 UTC 
*** Issue 9658 has been marked as a duplicate of this issue. ***
Comment 8 Oliver Specht 2003-01-23 12:57:46 UTC 
*** Issue 9685 has been marked as a duplicate of this issue. ***
Comment 9 Oliver Specht 2003-06-19 11:01:54 UTC 
Closed.