After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 89260 - GMime parser infinite loop
GMime parser infinite loop
Status: RESOLVED FIXED
Product: Pan
Classification: Other
Component: general
pre-0.13.0 betas
Other All
: Normal normal
: 0.13.0
Assigned To: Charles Kerr
Pan QA Team
Depends on:
Blocks:
 
 
Reported: 2002-07-28 14:56 UTC by Charles Kerr
Modified: 2006-06-18 04:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
the message that causes gmime to lock up (836 bytes, text/plain)
2002-07-28 14:57 UTC, Charles Kerr
Details

Description Charles Kerr 2002-07-28 14:56:27 UTC
William MacCracken writes at
http://mail.freesoftware.fsf.org/pipermail/pan-devel/2002-July/000121.html

  In alt.binaries.multimedia.buffy-v-slayer.repost a message, REQ: Please
  Post Buffy 4x16 Who Are You - Thank You Much!, 10 lines by "someone" on
  07.26 19:59 locks up Pan.

  Seemed strange to me.  I've been using Pan for months, I've not seen
  anything like it before. I can read any other message in the group.  It
  seemed so odd to me that i kept checking back on that one message (at
  least a dozen times) and every time it froze pan!

  Version 0.12.1 on Gentoo Linux.  Everyone else (on either MS or Mac,
  presumably) can read the message normaly.

  I'm not sending this 'cause i want to read that one message so
  badly, just to point out what seems from my end to be some wierdness
Comment 1 Charles Kerr 2002-07-28 14:57:16 UTC
Created attachment 10095 [details]
the message that causes gmime to lock up
Comment 2 Charles Kerr 2002-07-28 14:58:37 UTC
Christophe writes at
http://mail.freesoftware.fsf.org/pipermail/pan-devel/2002-July/000123.html

which causes an infinite loop in GMime's parser_step_from (in
gmime-parser.c): it continuously tries to add more data through
parser_fill.
Comment 3 Charles Kerr 2002-07-28 14:59:53 UTC
I've confirmed that this problem is still in GMime CVS HEAD,
passing the above attachment to test-parser hits the infinite
loop.
Comment 4 Jeffrey Stedfast 2002-07-29 05:51:20 UTC
yea, someone just reported this to me the other day.

should now be fixed in CVS (at least it is for me)
Comment 5 Christophe Lambin 2002-07-29 07:12:45 UTC
fejj: that commit broke the build:

gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. 	-I..\gmime 	-D_REENTRANT
-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include   	    -Wall -ggdb3
-I. -c gmime-parser.c
gmime-parser.c:35:32: gmime-message-part.h: No such file or directory
gmime-parser.c:39:20: strlib.h: No such file or directory
make: *** [gmime-parser.o] Error 1

Judging by the number of changes in that commit, we'll probably want
to  do a full sync with the gmime tree.
Comment 6 Jeffrey Stedfast 2002-07-29 18:44:14 UTC
oops, sorry bout that.
Comment 7 Christophe Lambin 2002-07-29 22:57:05 UTC
Charles kindly synced CVS.  This is now fixed in HEAD.