[Bug 676388] New: 32 bit mutt breaks with mbox files > 2 GB
https://bugzilla.novell.com/show_bug.cgi?id=676388 https://bugzilla.novell.com/show_bug.cgi?id=676388#c0 Summary: 32 bit mutt breaks with mbox files > 2 GB Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: koenig@linux.de QAContact: qa@suse.de Found By: --- Blocker: --- I've debugged/tested this issue with mutt-1.5.20, but 11.4/factory mutt-1.5.21-31.2.i586.rpm shows the same issues: at least mutt 1.5.20 and 1.5.21 (but not 1.5.18) have some issues with mbox files > 2 GB size. the attached patch below fixes these issues (at least for me;), maybe that's also the same fix for mutt ticket #3487 ?! try: open mbox file with size >2GB, select a mail which is positioned >2 GB in that mbox, open that mail (press return) ==> mail gets displayed ok. press "q" to return to subject browser, and open the same mail again with "return": mail display is broken. or: bouncing a mail with pos >2GB works *only* iff you do not display the mail before bouncing. if the mail first got displayed, the process of bouncing sends some trash snipps from the mbox. some debugging showed (for 1.5.21): in mutt_copy_header() in copy.c when calling mutt_copy_hdr() the value of "h->content->offset" got trashed (was negative) for the 2nd (broken) display of mails with pos >2GB. fixing some "long" types to "LOFF_T" mutt.h smime.c and handler.c fixed at least that displaying errors. doing some more code inspection for "long" types suggests that there might be similar issues in crypt-gpgme.c pgp.c mh.c (not 100% sure, please check!). the attached diff for mutt-1.5.21 (all changes included) applies to and builds fine with mutt 1.5.20 too, and solves the display problem there, too... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=676388
https://bugzilla.novell.com/show_bug.cgi?id=676388#c1
--- Comment #1 from Harald Koenig
https://bugzilla.novell.com/show_bug.cgi?id=676388
https://bugzilla.novell.com/show_bug.cgi?id=676388#c
Harald Koenig
https://bugzilla.novell.com/show_bug.cgi?id=676388
https://bugzilla.novell.com/show_bug.cgi?id=676388#c
zj jia
https://bugzilla.novell.com/show_bug.cgi?id=676388
https://bugzilla.novell.com/show_bug.cgi?id=676388#c2
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=676388
https://bugzilla.novell.com/show_bug.cgi?id=676388#c3
Marcus Meissner
https://bugzilla.novell.com/show_bug.cgi?id=676388
https://bugzilla.novell.com/show_bug.cgi?id=676388#c4
--- Comment #4 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=676388
https://bugzilla.novell.com/show_bug.cgi?id=676388#c5
Christian Dengler
https://bugzilla.novell.com/show_bug.cgi?id=676388
https://bugzilla.novell.com/show_bug.cgi?id=676388#c6
Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=676388
https://bugzilla.novell.com/show_bug.cgi?id=676388#c7
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=676388
https://bugzilla.novell.com/show_bug.cgi?id=676388#c8
Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=676388
https://bugzilla.novell.com/show_bug.cgi?id=676388#c
Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=676388
https://bugzilla.novell.com/show_bug.cgi?id=676388#c9
--- Comment #9 from Bernhard Wiedemann
participants (1)
-
bugzilla_noreply＠novell.com