Issue 46 of Bugs, issues and feature requests collector [pgui]
Title: | pgserver crash in pgstring/textbox code | ||
Status: | Pending | Security related: | No |
Description: | This bug manifests itself as a segfault during a memmove() call. You can cause it by opening Nifty and typing something into the minibuffer that gener... | ||
From: | micah | on |
May 6, 03 15:18
|
micah | Last update: |
~
|
|
Topic/class: | general/bug | Importance: | critical |
Version info: | SVN repository revision 3860 | ||
Transcript for Issue 46 (1 )
= Request - Entry #1 by micah on May 6, 2003 3:18 pm
This bug manifests itself as a segfault during a memmove() call. You can cause it by opening Nifty and typing something into the minibuffer that generates an exception, like "boing".
memmove() is being caleld from pgstring_insert_char(), with a negative length parameter. The pgstr_iterator passed to pgstring_insert_char() is invalid. (p->invalid==1 and p->offset is 1 whereas the string is empty)
I have a hunch this was caused by the textbox widget recently switching its default encoding from ascii to UTF-8.
This bug manifests itself as a segfault during a memmove() call. You can cause it by opening Nifty and typing something into the minibuffer that generates an exception, like "boing".
memmove() is being caleld from pgstring_insert_char(), with a negative length parameter. The pgstr_iterator passed to pgstring_insert_char() is invalid. (p->invalid==1 and p->offset is 1 whereas the string is empty)
I have a hunch this was caused by the textbox widget recently switching its default encoding from ascii to UTF-8.