Hello Mark,
Thanks very much for your effort.
I've compiled latest development release and strangely enough with this
version (imap-2006d.DEV.SNAP-0611131848) I cannot reproduce the "move
message" problem.
Just for the record here's transcript of gdb session from our test
system running 2006c1.
css5{root}#ps -ef | grep imapd
ebor 10900 1024 0 05:48:46 ? 0:00 imapd
root 10902 10222 0 05:48:56 pts/0 0:00 grep imapd
ebor 10899 1024 0 05:48:40 ? 0:00 imapd
css5{root}#gdb imapd
HP gdb 5.5.0 for PA-RISC 1.1 or 2.0 (narrow), HP-UX 11.00
and target hppa1.1-hp-hpux11.00.
Copyright 1986 - 2001 Free Software Foundation, Inc.
Hewlett-Packard Wildebeest 5.5.0 (based on GDB) is covered by the
GNU General Public License. Type "show copying" to see the conditions to
change it and/or distribute copies. Type "show warranty" for
warranty/support.
..
(gdb) set follow-fork-mode child
(gdb) attach 10900
Attaching to program: /home/ebor/src/imap-2006c1/imapd/imapd, process 10900
warning: The shared libraries were not privately mapped; setting a
breakpoint in a shared library will not work until you rerun the
program; stepping over longjmp calls will not work as expected.
warning: reading `r3' register: No data
0xc020d488 in _select_sys+0x10 () from /usr/lib/libc.2
(gdb) continue
Continuing.
[New process 10904]
Detaching from program: /home/ebor/src/imap-2006c1/imapd/imapd, process
10900
Attaching after fork to process 10904
Program received signal SIGBUS, Bus error
si_code: 0 - BUS_UNKNOWN - Unknown Error.
[Switching to process 10904]
0x6bf00 in unix_copy (stream=0x40037540, sequence=0x40018e6c "81",
mailbox=0x40018e70 "INBOX", options=1) at unix.c:974
974 if (!tstream->rdonly) ((UNIXLOCAL *) tstream->local)->dirty = T;
(gdb) bt
#0 0x6bf00 in unix_copy (stream=0x40037540, sequence=0x40018e6c "81",
mailbox=0x40018e70 "INBOX", options=1) at unix.c:974
#1 0x2eb10 in safe_copy (dtb=warning: reading `' register: Invalid argument
0x2, stream=Error accessing memory address 0x425f5c: Bad address.
) at flocksim.c:611
#2 0x395f8 in mail_copy_full (stream=Error accessing memory address
0x65616473: Bad address.
) at mail.c:2495
#3 0x16294 in main (argc=838860865, argv=0x0) at imapd.c:659
(gdb) detach
Detaching from program: /home/ebor/src/imap-2006c1/imapd/imapd, process
10904
(gdb) quit
css5{root}#
Regards,
Ermin
Mark Crispin wrote:
I have spent most of today thoroughly analyzing that code, and have failed
utterly in multiple attempts to reproduce the problem.
I don't see how that instruction could fail. tstream is referenced
repeatedly earlier in the function, and the dirty flag is an ordinary flag
early in the local data part of the structure.
Commenting out that instruction is definitely not the right thing to do,
as it is necessary to update the mailbox metadata and severe performance
problems result if that doesn't happen.
Have you tried the imap-2006d development version? Is there any way that
you can give me access to your system, preferably with a script that
details how to reproduce the problem?
-- Mark --
http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.
_______________________________________________
Imap-uw mailing list
[email protected]
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
