view etc/toolbar/replace-xx.xpm @ 5857:6ec4964c1687

Be more careful about echo_buf arithmetic, event-stream.c. src/ChangeLog addition: 2015-03-12 Aidan Kehoe <kehoea@parhasard.net> * event-stream.c (lookup_command_event): Check whether echo_buf_fill_pointer is negative before using it in arithmetic, avoiding a crash in GC. Oddly the old code didn't do this check and didn't crash, but its echo_buf was from malloced memory, not from our string data, so there may have been more room to manoeuvre.
author Aidan Kehoe <kehoea@parhasard.net>
date Thu, 12 Mar 2015 23:31:42 +0000
parents 7910031dd78a
children
line wrap: on
line source

/* XPM */

/* This file is part of XEmacs.

XEmacs is free software: you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
Free Software Foundation, either version 3 of the License, or (at your
option) any later version.

XEmacs is distributed in the hope that it will be useful, but WITHOUT
ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License
for more details.

You should have received a copy of the GNU General Public License
along with XEmacs.  If not, see <http://www.gnu.org/licenses/>. */

static char * replace[] = {
"28 28 2 1",
"X	c Gray75 s backgroundToolBarColor",
"o	c Gray60",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"XXXXXXooXXXXooooXXXXXXXXXXXX",
"XXXXXXooXXXXooXXoXXXXXXXXXXX",
"XXXXXoXooXXXooXXoXXXXXXXXXXX",
"XXXXXoXooXXXoooooXXXXXXXXXXX",
"XXXXoXXXooXXooXXXoXXoooXXXXX",
"XXXXooooooXXooXXXoXXooXXXXXX",
"XXXoXXXXXooXooXXXoXXoXoXXXXX",
"XXXoXXXXXooXoooooXXXXXXoXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXoXXXX",
"XXXXXXXXXXXXoXXXXXXXXXXoXXXX",
"XXXXXXXXXXXoXXXXXXXXXXXoXXXX",
"XXXXXXXXXXXoXXXXXXXXXXoXXXXX",
"XXXXXXXXXXoXXXXXXXXXXoXXXXXX",
"XXXXXXXXXoXXXXXXXXXXXXXXXXXX",
"XXXXXXXXXoXXXXXXooooXXXXXXXX",
"XXXXXXXXoXXXXXXooXXXoXXXXXXX",
"XXXXXoXoXXXXXXXooXXXXXXXXXXX",
"XXXXXooXXXXXXXXooXXXXXXXXXXX",
"XXXXXooooXXXXXXooXXXXXXXXXXX",
"XXXXXooXXXXXXXXooXXXXXXXXXXX",
"XXXXXXXXXXXXXXXooXXXoXXXXXXX",
"XXXXXXXXXXXXXXXXooooXXXXXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"XXXXXXXXXXXXXXXXXXXXXXXXXXXX"};