STR #1176

FLTK matrix user chat room
(using Element browser app)   FLTK gitter user chat room   GitHub FLTK Project   FLTK News RSS Feed  
  FLTK Apps      FLTK Library      Forums      Links     Login 
 Home  |  Articles & FAQs  |  Bugs & Features  |  Documentation  |  Download  |  Screenshots  ]
 

Return to Bugs & Features | Roadmap 1.1 ]

STR #1176

Application:FLTK Library
Duplicate Of:STR #1150
Status:1 - Closed w/Resolution
Priority:4 - High, e.g. key functionality not working
Scope:2 - Specific to an operating system
Subsystem:FLUID
Summary:Fluid crash on Win2000
Version:1.1.7
Created By:Dima
Assigned To:matt
Fix Version:1.1-current
Update Notification:

Receive EMails Don't Receive EMails

Trouble Report Files:


Name/Time/Date Filename/Size top right image
 
#1 Dima
01:05 Feb 13, 2006
tuner.fl
1k
 
bottom left image   bottom right image

Trouble Report Comments:


Name/Time/Date Text top right image
 
#1 Dima
01:05 Feb 13, 2006
It seems that it does not like russian language (1251 codepage).
(example: tuner.fl)

windows shows an error:
instruction addressed 0x0042289d accessed memory at address 0x00, the memory location cannot be read
 
 
#2 mike
05:11 Feb 13, 2006
What compiler are you using?

Can you run FLUID from a debugger and tell us where it is crashing?
 
 
#3 Dima
04:51 Mar 02, 2006
Using MinGW, trying to debug with gdb :-)
function crashed: file.cxx:

static void read_children(Fl_Type *p, int paste)

Fluid v 2.0.0 behaves the same with this file
 
 
#4 matt
06:43 Mar 27, 2006
MinGW already had prombles with non-ASCII characters, IIRC. I beleive it was the "tolower" function that would barf when receiving a "negative" character.

If you have the time, please compile FLTK in debug mode (--enable_debug), start your test program using "dgb". When the programcrashes and returns to the debugger, enter "bt" to get a stack dump. Then upload the stack dump to this STR. Also, if you see variables involved in the crashing call, print them out to using "print xyz".

Thanks
 
 
#5 fabien
11:08 Apr 04, 2006
does it still happen now (r4899?)  
 
#6 matt
21:04 Apr 19, 2006
This should be fixed as good as possible. Please verify.

However:
- fltk1 does not support the Russian code page (fltk2 does)
- MinGW has a bug in the character classification functions
 
bottom left image   bottom right image

Return to Bugs & Features ]

 
 

Comments are owned by the poster. All other content is copyright 1998-2022 by Bill Spitzak and others. This project is hosted by The FLTK Team. Please report site problems to 'erco@seriss.com'.