Michael Schmitt <[EMAIL PROTECTED]> writes:
| Of course, I cannot blame you for problems in some external libraries.
| But maybe you are willing to quickly browse through the list of warning
| to make sure that it is a problem of my Sun environment? As I stated
| before I never had such problems before. Moreover, I do not have any
| problems with characters other than " ".
You are sure your X header files and libraires match?
I have no clue as to what is going on.
| UMR: Uninitialized memory read
| This is occurring while in:
| HandleComposeSequence [KeyBind.c]
| _XTranslateKeySym [KeyBind.c]
| XLookupString [KeyBind.c]
| _MbLookupString [XSunIMIF.c]
| XmbLookupString [ICWrap.c]
| int LyXLookupString(_XEvent*,char*,int,unsigned long*)
| [lyxlookup.C:160]
With a debugger you should be able to find out what is happening here,
if LyXLookupString is calling XmbLookupString with wring/faulty args.
But it seems strange since
[...]
| Reading 4 bytes from 0xff164b88 between the heap and the stack.
| Address 0xff164b88 is 340 bytes past start of global variable
| "compose_table".
| This is defined in XSunOMIF.c.
| UMR: Uninitialized memory read
| This is occurring while in:
| HandleComposeSequence [KeyBind.c]
| _XTranslateKeySym [KeyBind.c]
| XLookupString [KeyBind.c]
| do_keyboard [libforms.a]
| do_interaction_step [libforms.a]
here you get the same thing without going through any LyX code at all.
Have you locally changed the compose tables?
(some X file, don't ask me where to find it...)
Does this happen on all space inserts? Regardless of what char it is
after, what paragraph it is in. And you find _none_ of these errors in
lyx-1.1.3?
Lgb
