[Dovecot] problem with mail_full_filesystem_access = yes

Pašek Ladislav pasek at valbek.cz
Wed Aug 4 00:09:03 EEST 2010


Thanks for hint. This is output from gdb bt full but I have no clue what to find in it:

#0  0x0000003129a32ce2 in unsetenv () from /lib64/libc.so.6
No symbol table info available.
#1  0x000000000041a078 in config_file_init (argc=<value optimized out>, argv=<value optimized out>) at deliver.c:497
No locals.
#2  main (argc=<value optimized out>, argv=<value optimized out>) at deliver.c:1062
        _data_stack_cur_id = 2
        config_path = 0x4aa3e6 "/etc/dovecot.conf"
        mailbox = 0x4b32f5 "INBOX"
        auth_socket = <value optimized out>
        home = <value optimized out>
        destaddr = 0x0
        user = 0x7fff50d9272b "pasek at valbek.cz"
        errstr = <value optimized out>
        path = 0x0
        orig_user = <value optimized out>
        extra_fields = {arr = {buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0}
        mail_user = <value optimized out>
        raw_mail_user = <value optimized out>
        raw_ns = <value optimized out>
        e = <value optimized out>
        box = <value optimized out>
        raw_box = <value optimized out>
        input = <value optimized out>
        t = <value optimized out>
        headers_ctx = <value optimized out>
        mail = <value optimized out>
        cwd = "\360>\265s\255*\000\000ù`)1\000\000\000\001\000\000\000\000\000\000\000\360\071\265s\255*\000\000\020\004\331P\377\177\000\000\000\000\000\000\000\000\000\000\353\214 at 41\000\000\000\266\270`)1\000\000\000\001\000\000\000\000\000\000\000\030\065\265s\255*\000\000P\b\331P\377\177\000\000\000\000\000\000\000\000\000\000\300\214 at 41\000\000\000\266\270`)1\000\000\000\001\000\000\000\000\000\000\000H0\265s\255*\000\000\200\b\331P\377\177\000\000\000\000\000\000\000\000\000\000\260\214 at 41\000\000\000\266\270`)1\000\000\000\001\000\000\000\377\177\000\000\200+\265s\255*\000\000\260\b\331P\377\177\000\000\000\000\000\000\000\000\000\000\243\214 at 41\000\000\000\266\270`)1\000\000\000\001\000\000\000\000\000\000\000\250&\265s\255*\000\000\340\b\331P\377\177\000\000\000\000\000\000\000\000\000\000\217\214 at 41\000\000\000\266\270`"...
        process_euid = 0
        stderr_rejection = false
        keep_environment = false
        user_auth = true
        mtime = <value optimized out>
        i = <value optimized out>
        ret = <value optimized out>
        userdb_pool = 0x0
        str = <value optimized out>
        error = MAIL_ERROR_NONE


 Pátek, 30 Červenec, 2010 21:43 CEST, Timo Sirainen <tss at iki.fi> napsal:

> On 30.7.2010, at 18.44, Ladislav Pašek wrote:
> 
> > Thanks for hint. So I checked with strace and its output is here:
> 
> Strace output isn't very helpful for crashes. gdb backtrace would show exactly where it crashes. If you can crash it by running
> 
> deliver ..params.. < mail-file
> 
> then easiest way to get backtrace is to run it like:
> 
> gdb --args deliver ..params..
> run < mail-file
> bt full
> 




More information about the dovecot mailing list