• Re: fmail linux malloc(): invalid next size (unsorted)

    From Wilfred van Velzen@2:280/464 to Fernando Toledo on Mon Nov 11 22:38:17 2024
    Hi Fernando,

    On 2024-11-11 18:07:34, you wrote to Fidonet.FMAIL_HELP:

    Hi People! I just try to use fmail (I've never used it before, so I
    may be doing something wrong)

    I compiled it on debian12 with no errors (latests git from SF.net),

    I haven't tested it on any debian version yet...

    fdconfig works and I started configuring some things.

    But if you want to do a fmail toss or scan etc, they all fail with the following error message

    If you have any insight into where to start looking, it would be appreciated

    ragnarok@ragnarok-pc:~/fido/fmail$ ./fmail toss
    FMail-lnx64-2.3.1.0 - The Fast Echomail Processor
    Copyright (C) 1991-2024 by FMail Developers - All rights reserved



    Scanning netmail directory...

    malloc(): invalid next size (unsorted)
    Abortado
    ...

    #9 0x00007ffff7e7bdd2 in opendir_tail (fd=4) at ../sysdeps/unix/sysv/linux/opendir.c:63
    #10 0x0000555555589fcf in Delete ()
    #11 0x0000555555577d86 in initMsg ()
    #12 0x000055555556ef78 in Toss ()
    #13 0x00005555555722a9 in main ()

    It would help if you could compile in debug mode, with symbols present in the compiled executable, but it seems to come from these lines:

    Line 238 in msgmsg.c:
    Delete(config.netPath, "*."MBEXTB);
    if (*config.pmailPath)
    Delete(config.pmailPath, "*."MBEXTB);

    Could it be you haven't set the netmail path directory for instance?


    Bye, Wilfred.

    --- FMail-lnx64 2.3.2.4-B20240523
    * Origin: FMail development HQ (2:280/464)
  • From Fernando Toledo@4:902/26 to Wilfred van Velzen on Mon Nov 11 21:07:29 2024
    El 11/11/24 a las 18:38, Wilfred van Velzen escribió:

    Alo! Wilfred!


    FT> #9 0x00007ffff7e7bdd2 in opendir_tail (fd=4) at
    FT> ../sysdeps/unix/sysv/linux/opendir.c:63
    FT> #10 0x0000555555589fcf in Delete ()
    FT> #11 0x0000555555577d86 in initMsg ()
    FT> #12 0x000055555556ef78 in Toss ()
    FT> #13 0x00005555555722a9 in main ()

    It would help if you could compile in debug mode, with symbols present in the compiled executable, but it seems to come from these lines:

    I run with debug symbols:

    Reading symbols from ./fmail...
    (gdb) set args toss
    (gdb) r
    Starting program: /home/ragnarok/fido/fmail/fmail toss
    [Thread debugging using libthread_db enabled]
    Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". FMail-lnx64-2.3.1.0 - The Fast Echomail Processor
    Copyright (C) 1991-2024 by FMail Developers - All rights reserved

    DEBUG cwd: /home/ragnarok/fido/fmail
    DEBUG arg 0: /home/ragnarok/fido/fmail/fmail
    DEBUG arg 1: toss
    DEBUG replaceDrive = ""
    DEBUG configPath = "/home/ragnarok/fido/fmail/"
    DEBUG gmtOffset=-10800 daylight=1 timezone=10800 tzname=-03--03


    Scanning netmail directory...

    DEBUG Delete-ing: /home/ragnarok/fido/fmail/netmail/*.fml
    malloc(): invalid next size (unsorted)

    Program received signal SIGABRT, Aborted.
    __pthread_kill_implementation (threadid=<optimized out>,
    signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
    44 ./nptl/pthread_kill.c: No existe el fichero o el directorio.
    (gdb) bt
    #0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
    #1 0x00007ffff7e36f1f in __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78
    #2 0x00007ffff7de7fb2 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
    #3 0x00007ffff7dd2472 in __GI_abort () at ./stdlib/abort.c:79
    #4 0x00007ffff7e2b430 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7ffff7f45459 "%s\n")
    at ../sysdeps/posix/libc_fatal.c:155
    #5 0x00007ffff7e4083a in malloc_printerr (str=str@entry=0x7ffff7f48590 "malloc(): invalid next size (unsorted)")
    at ./malloc/malloc.c:5660
    #6 0x00007ffff7e43974 in _int_malloc (av=av@entry=0x7ffff7f7ec60 <main_arena>, bytes=bytes@entry=4096) at ./malloc/malloc.c:4001
    #7 0x00007ffff7e44a8a in __GI___libc_malloc (bytes=bytes@entry=4096) at ./malloc/malloc.c:3315
    #8 0x00007ffff7e218cc in __GI__IO_file_doallocate (fp=0x7fffffff3810)
    at ./libio/filedoalloc.c:101
    #9 0x00007ffff7e2f0a0 in __GI__IO_doallocbuf (fp=0x7fffffff3810) at ./libio/libioP.h:947
    #10 __GI__IO_doallocbuf (fp=fp@entry=0x7fffffff3810) at ./libio/genops.c:342 #11 0x00007ffff7e2ccec in _IO_new_file_seekoff (fp=0x7fffffff3810,
    offset=0, dir=1, mode=<optimized out>) at ./libio/fileops.c:937
    #12 0x00007ffff7e2df82 in _IO_new_file_attach
    (fp=fp@entry=0x7fffffff3810, fd=fd@entry=4) at ./libio/libioP.h:947
    #13 0x00007ffff7e2a50d in __vdprintf_internal (d=4,
    format=0x5555555937f0 "%02u:%02u:%02u.%03u ",
    arg=arg@entry=0x7fffffff3a10,
    mode_flags=mode_flags@entry=0) at ./libio/iovdprintf.c:44
    #14 0x00007ffff7dfdd76 in __GI___dprintf (d=<optimized out>,
    format=<optimized out>) at ./stdio-common/dprintf.c:30
    #15 0x0000555555577734 in writeLogLine (logHandle=4, s=0x7fffffff4be0
    "DEBUG Delete-ing: /home/ragnarok/fido/fmail/netmail/*.fml")
    at /home/ragnarok/fido/fmail-code/log.c:117
    #16 0x0000555555577c59 in logEntry (s=0x7fffffff4be0 "DEBUG Delete-ing: /home/ragnarok/fido/fmail/netmail/*.fml", entryType=32768,
    errorLevel=0) at /home/ragnarok/fido/fmail-code/log.c:251
    #17 0x0000555555577b2f in logEntryf (entryType=32768, errorLevel=0, fmt=0x55555559556b "DEBUG Delete-ing: %s%s")
    at /home/ragnarok/fido/fmail-code/log.c:217
    #18 0x000055555558ab73 in Delete (path=0x5555555add10 <config+560> "/home/ragnarok/fido/fmail/netmail/",
    wildCard=0x5555555939d7 "*.fml") at /home/ragnarok/fido/fmail-code/utils.c:371
    #19 0x000055555557857c in initMsg (noAreaFix=0) at /home/ragnarok/fido/fmail-code/msgmsg.c:241
    #20 0x000055555556f413 in Toss (argc=2, argv=0x7fffffffdcf8) at /home/ragnarok/fido/fmail-code/fmail.c:986
    #21 0x0000555555572902 in main (argc=2, argv=0x7fffffffdcf8) at /home/ragnarok/fido/fmail-code/fmail.c:2065
    (gdb)





    Line 238 in msgmsg.c:
    Delete(config.netPath, "*."MBEXTB);
    if (*config.pmailPath)
    Delete(config.pmailPath, "*."MBEXTB);

    Could it be you haven't set the netmail path directory for instance?

    I setup all directories at System Info->Directories (all have absolute
    paths and these exists)

    I dont have *.fml files at netmail directory as see the debug line:

    DEBUG Delete-ing: /home/ragnarok/fido/fmail/netmail/*.fml
    --- SBBSecho 3.21-Linux
    * Origin: Dock Sud BBS - http://bbs.docksud.com.ar (4:902/26)
  • From Fernando Toledo@4:902/26 to Fernando Toledo on Mon Nov 11 23:49:11 2024
    El 11/11/24 a las 21:07, Fernando Toledo escribió:
    El 11/11/24 a las 18:38, Wilfred van Velzen escribió:

    I think that I found sometihng like a bug.

    I save the area as ESP.PRUEBAS at area Mgr, then close, save config and
    reopen fconfig. Finally, the Area name seems that broken.

    I paste a capture here:

    https://downloads.bbs.docksud.com.ar/tmp/fmail_area.png

    Saludos!
    --- SBBSecho 3.21-Linux
    * Origin: Dock Sud BBS - http://bbs.docksud.com.ar (4:902/26)
  • From Fernando Toledo@4:902/26 to Fernando Toledo on Tue Nov 12 00:21:43 2024
    El 11/11/24 a las 23:49, Fernando Toledo escribió:
    El 11/11/24 a las 21:07, Fernando Toledo escribió:
    El 11/11/24 a las 18:38, Wilfred van Velzen escribió:

    I think that I found sometihng like a bug.

    I save the area as ESP.PRUEBAS at area Mgr, then close, save config and reopen fconfig.  Finally, the Area name seems that broken.

    I paste a capture here:

    https://downloads.bbs.docksud.com.ar/tmp/fmail_area.png

    Saludos!

    the issue seems to raise when call initAreaInfo() at line 175, i think
    that is here, the area name is not read corretly

    (sorry, I don't have more skills on C code to help)


    (gdb) set args mgr
    (gdb) r
    Starting program: /home/ragnarok/fido/fmail/fmail mgr
    [Thread debugging using libthread_db enabled]
    Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". FMail-lnx64-2.3.1.0 - The Fast Echomail Processor
    Copyright (C) 1991-2024 by FMail Developers - All rights reserved

    DEBUG cwd: /home/ragnarok/fido/fmail
    DEBUG arg 0: /home/ragnarok/fido/fmail/fmail
    DEBUG arg 1: mgr
    DEBUG replaceDrive = ""
    DEBUG configPath = "/home/ragnarok/fido/fmail/"
    DEBUG gmtOffset=-10800 daylight=1 timezone=10800 tzname=-03--03


    malloc(): invalid next size (unsorted)

    Program received signal SIGABRT, Aborted.
    __pthread_kill_implementation (threadid=<optimized out>,
    signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
    44 ./nptl/pthread_kill.c: No existe el fichero o el directorio.
    (gdb) bt
    #0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
    #1 0x00007ffff7e36f1f in __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78
    #2 0x00007ffff7de7fb2 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
    #3 0x00007ffff7dd2472 in __GI_abort () at ./stdlib/abort.c:79
    #4 0x00007ffff7e2b430 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7ffff7f45459 "%s\n") at ../sysdeps/posix/libc_fatal.c:155
    #5 0x00007ffff7e4083a in malloc_printerr (str=str@entry=0x7ffff7f48590 "malloc(): invalid next size (unsorted)") at ./malloc/malloc.c:5660
    #6 0x00007ffff7e43974 in _int_malloc (av=av@entry=0x7ffff7f7ec60 <main_arena>, bytes=3) at ./malloc/malloc.c:4001
    #7 0x00007ffff7e44a8a in __GI___libc_malloc (bytes=<optimized out>) at ./malloc/malloc.c:3315
    #8 0x0000555555566563 in initAreaInfo () at /home/ragnarok/fido/fmail-code/areainfo.c:175
    #9 0x00005555555724f2 in Mgr (argc=2, argv=0x7fffffffdcf8) at /home/ragnarok/fido/fmail-code/fmail.c:1966
    #10 0x0000555555572ab6 in main (argc=2, argv=0x7fffffffdcf8) at /home/ragnarok/fido/fmail-code/fmail.c:2077
    --- SBBSecho 3.21-Linux
    * Origin: Dock Sud BBS - http://bbs.docksud.com.ar (4:902/26)
  • From Tommi Koivula@2:221/6.600 to Wilfred van Velzen on Tue Nov 12 10:38:07 2024
    Hi Wilfred.

    11 Nov 24 22:38, you wrote to Fernando Toledo:

    Hi People! I just try to use fmail (I've never used it before, so I
    may be doing something wrong)

    I compiled it on debian12 with no errors (latests git from SF.net),

    I haven't tested it on any debian version yet...

    Debian 11.11 here. Works.

    gcc version 10.2.1 20210110 (Debian 10.2.1-6)

    'Tommi

    ---
    * Origin: FPoint (2:221/6.600)
  • From Wilfred van Velzen@2:280/464.112 to Fernando Toledo on Tue Nov 12 09:36:51 2024
    Hi Fernando,

    On 11 Nov 24 21:07, Fernando Toledo wrote to Wilfred van Velzen:
    about: "Re: fmail linux malloc(): invalid next size (unsorted)":

    FT> #9 0x00007ffff7e7bdd2 in opendir_tail (fd=4) at
    FT> ../sysdeps/unix/sysv/linux/opendir.c:63
    FT> #10 0x0000555555589fcf in Delete ()
    FT> #11 0x0000555555577d86 in initMsg ()
    FT> #12 0x000055555556ef78 in Toss ()
    FT> #13 0x00005555555722a9 in main ()

    It would help if you could compile in debug mode, with symbols present in
    the compiled executable, but it seems to come from these lines:

    I run with debug symbols:

    Ok great...

    Reading symbols from ./fmail...
    (gdb) set args toss
    (gdb) r
    Starting program: /home/ragnarok/fido/fmail/fmail toss
    [Thread debugging using libthread_db enabled]
    Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". FMail-lnx64-2.3.1.0 - The Fast Echomail Processor
    Copyright (C) 1991-2024 by FMail Developers - All rights reserved

    DEBUG cwd: /home/ragnarok/fido/fmail
    DEBUG arg 0: /home/ragnarok/fido/fmail/fmail
    DEBUG arg 1: toss
    DEBUG replaceDrive = ""
    DEBUG configPath = "/home/ragnarok/fido/fmail/"
    DEBUG gmtOffset=-10800 daylight=1 timezone=10800 tzname=-03--03


    Scanning netmail directory...

    DEBUG Delete-ing: /home/ragnarok/fido/fmail/netmail/*.fml
    malloc(): invalid next size (unsorted)

    Program received signal SIGABRT, Aborted.
    __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
    44 ./nptl/pthread_kill.c: No existe el fichero o el directorio.
    (gdb) bt
    #0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
    #1 0x00007ffff7e36f1f in __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78
    #2 0x00007ffff7de7fb2 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
    #3 0x00007ffff7dd2472 in __GI_abort () at ./stdlib/abort.c:79
    #4 0x00007ffff7e2b430 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7ffff7f45459 "%s\n")
    at ../sysdeps/posix/libc_fatal.c:155
    #5 0x00007ffff7e4083a in malloc_printerr (str=str@entry=0x7ffff7f48590 "malloc(): invalid next size (unsorted)")
    at ./malloc/malloc.c:5660
    #6 0x00007ffff7e43974 in _int_malloc (av=av@entry=0x7ffff7f7ec60 <main_arena>, bytes=bytes@entry=4096) at ./malloc/malloc.c:4001
    #7 0x00007ffff7e44a8a in __GI___libc_malloc (bytes=bytes@entry=4096) at ./malloc/malloc.c:3315
    #8 0x00007ffff7e218cc in __GI__IO_file_doallocate (fp=0x7fffffff3810)
    at ./libio/filedoalloc.c:101
    #9 0x00007ffff7e2f0a0 in __GI__IO_doallocbuf (fp=0x7fffffff3810) at ./libio/libioP.h:947
    #10 __GI__IO_doallocbuf (fp=fp@entry=0x7fffffff3810) at ./libio/genops.c:342 #11 0x00007ffff7e2ccec in _IO_new_file_seekoff (fp=0x7fffffff3810, offset=0, dir=1, mode=<optimized out>) at ./libio/fileops.c:937 #12 0x00007ffff7e2df82 in _IO_new_file_attach
    (fp=fp@entry=0x7fffffff3810, fd=fd@entry=4) at ./libio/libioP.h:947 #13 0x00007ffff7e2a50d in __vdprintf_internal (d=4, format=0x5555555937f0 "%02u:%02u:%02u.%03u ", arg=arg@entry=0x7fffffff3a10,
    mode_flags=mode_flags@entry=0) at ./libio/iovdprintf.c:44
    #14 0x00007ffff7dfdd76 in __GI___dprintf (d=<optimized out>, format=<optimized out>) at ./stdio-common/dprintf.c:30
    #15 0x0000555555577734 in writeLogLine (logHandle=4, s=0x7fffffff4be0 "DEBUG Delete-ing: /home/ragnarok/fido/fmail/netmail/*.fml")
    at /home/ragnarok/fido/fmail-code/log.c:117

    So here it seems to be happening when logging a debug line... Strange...

    #16 0x0000555555577c59 in logEntry (s=0x7fffffff4be0 "DEBUG
    Delete-ing:
    /home/ragnarok/fido/fmail/netmail/*.fml", entryType=32768,
    errorLevel=0) at /home/ragnarok/fido/fmail-code/log.c:251
    #17 0x0000555555577b2f in logEntryf (entryType=32768, errorLevel=0, fmt=0x55555559556b "DEBUG Delete-ing: %s%s")
    at /home/ragnarok/fido/fmail-code/log.c:217
    #18 0x000055555558ab73 in Delete (path=0x5555555add10 <config+560> "/home/ragnarok/fido/fmail/netmail/",
    wildCard=0x5555555939d7 "*.fml") at /home/ragnarok/fido/fmail-code/utils.c:371
    #19 0x000055555557857c in initMsg (noAreaFix=0) at /home/ragnarok/fido/fmail-code/msgmsg.c:241
    #20 0x000055555556f413 in Toss (argc=2, argv=0x7fffffffdcf8) at /home/ragnarok/fido/fmail-code/fmail.c:986
    #21 0x0000555555572902 in main (argc=2, argv=0x7fffffffdcf8) at /home/ragnarok/fido/fmail-code/fmail.c:2065
    (gdb)



    Line 238 in msgmsg.c:
    Delete(config.netPath, "*."MBEXTB);
    if (*config.pmailPath)
    Delete(config.pmailPath, "*."MBEXTB);

    Could it be you haven't set the netmail path directory for instance?

    I setup all directories at System Info->Directories (all have absolute paths and these exists)

    Ok...

    I dont have *.fml files at netmail directory as see the debug line:

    Well that is OK. The routine searches them and deletes them when they exist.


    Wilfred.

    --- FMail-W64 2.3.2.3-B20240423
    * Origin: point@work (2:280/464.112)
  • From Wilfred van Velzen@2:280/464.112 to Fernando Toledo on Tue Nov 12 09:58:44 2024
    Hi Fernando,

    On 11 Nov 24 23:49, Fernando Toledo wrote to Fernando Toledo:
    about: "Re: fmail linux malloc(): invalid next size (unsorted)":

    I think that I found sometihng like a bug.

    I save the area as ESP.PRUEBAS at area Mgr, then close, save config and reopen fconfig. Finally, the Area name seems that broken.

    I paste a capture here:

    https://downloads.bbs.docksud.com.ar/tmp/fmail_area.png

    Did you fill in a JAM MB name? Or (hudson) board number?

    Also I find the Write level (5706) rather strange...


    Wilfred.

    --- FMail-W64 2.3.2.3-B20240423
    * Origin: point@work (2:280/464.112)
  • From Wilfred van Velzen@2:280/464.112 to Fernando Toledo on Tue Nov 12 10:18:37 2024
    Hi Fernando,

    On 12 Nov 24 00:21, Fernando Toledo wrote to Fernando Toledo:
    about: "Re: fmail linux malloc(): invalid next size (unsorted)":

    I think that I found sometihng like a bug.

    I save the area as ESP.PRUEBAS at area Mgr, then close, save config and
    reopen fconfig.  Finally, the Area name seems that broken.

    I paste a capture here:

    https://downloads.bbs.docksud.com.ar/tmp/fmail_area.png

    Saludos!

    the issue seems to raise when call initAreaInfo() at line 175, i think that is here, the area name is not read corretly

    This seems to be the same error, but in a different place in the code...

    malloc(): invalid next size (unsorted)

    Btw: Have you tried running 1 of the precompiled linux versions instead?

    https://sourceforge.net/projects/fmail/files/FMail/2.3/FMail-lnx64-2.3.1.0.zip/ download
    https://sourceforge.net/projects/fmail/files/FMail/2.3/FMail-lnx32-2.3.1.0.zip/ download


    Wilfred.

    --- FMail-W64 2.3.2.3-B20240423
    * Origin: point@work (2:280/464.112)
  • From Wilfred van Velzen@2:280/464 to Tommi Koivula on Tue Nov 12 10:47:55 2024
    Hi Tommi,

    On 2024-11-12 10:38:07, you wrote to me:

    I compiled it on debian12 with no errors (latests git from SF.net),

    I haven't tested it on any debian version yet...

    Debian 11.11 here. Works.

    gcc version 10.2.1 20210110 (Debian 10.2.1-6)

    Thanks for the information!


    Bye, Wilfred.

    --- FMail-lnx64 2.3.2.4-B20240523
    * Origin: FMail development HQ (2:280/464)
  • From Fernando Toledo@4:902/26 to Wilfred van Velzen on Tue Nov 12 20:03:25 2024
    El 12/11/24 a las 06:18, Wilfred van Velzen escribió:
    Hi Fernando,

    FT> malloc(): invalid next size (unsorted)

    Btw: Have you tried running 1 of the precompiled linux versions instead?

    https://sourceforge.net/projects/fmail/files/FMail/2.3/FMail-lnx64-2.3.1.0.zip/ download
    https://sourceforge.net/projects/fmail/files/FMail/2.3/FMail-lnx32-2.3.1.0.zip/ download

    I will test asap
    --- SBBSecho 3.21-Linux
    * Origin: Dock Sud BBS - http://bbs.docksud.com.ar (4:902/26)
  • From Fernando Toledo@4:902/26 to Wilfred van Velzen on Tue Nov 12 20:06:18 2024
    El 12/11/24 a las 05:58, Wilfred van Velzen escribió:
    Hi Fernando,

    On 11 Nov 24 23:49, Fernando Toledo wrote to Fernando Toledo:
    about: "Re: fmail linux malloc(): invalid next size (unsorted)":

    FT> I think that I found sometihng like a bug.

    FT> I save the area as ESP.PRUEBAS at area Mgr, then close, save config and
    FT> reopen fconfig. Finally, the Area name seems that broken.

    FT> I paste a capture here:

    FT> https://downloads.bbs.docksud.com.ar/tmp/fmail_area.png

    Did you fill in a JAM MB name? Or (hudson) board number?

    I supose to use JAM no hudson..

    Also I find the Write level (5706) rather strange...


    yes.. Maybe the fmail cmd corrupt the config settings after run it.
    --- SBBSecho 3.21-Linux
    * Origin: Dock Sud BBS - http://bbs.docksud.com.ar (4:902/26)
  • From Fernando Toledo@4:902/26 to Tommi Koivula on Tue Nov 12 20:15:38 2024
    El 12/11/24 a las 05:38, Tommi Koivula escribió:
    Hi Wilfred.

    11 Nov 24 22:38, you wrote to Fernando Toledo:

    FT>> Hi People! I just try to use fmail (I've never used it before, so I
    FT>> may be doing something wrong)
    WV>
    FT>> I compiled it on debian12 with no errors (latests git from SF.net),
    WV>
    WV> I haven't tested it on any debian version yet...

    Debian 11.11 here. Works.

    gcc version 10.2.1 20210110 (Debian 10.2.1-6)

    'Tommi


    ragnarok@ragnarok-pc:~/fido/fmail$ gcc -v
    Using built-in specs.
    COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/12/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
    OFFLOAD_TARGET_DEFAULT=1
    Target: x86_64-linux-gnu
    Configured with: ../src/configure -v --with-pkgversion='Debian
    12.2.0-14' --with-bugurl=file:///usr/share/doc/gcc-12/README.Bugs --enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-12 --program-prefix=x86_64-linux-gnu- --enable-shared
    --enable-linker-build-id --libexecdir=/usr/lib
    --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib
    --enable-libphobos-checking=release --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none=/build/gcc-12-bTRWOB/gcc-12-12.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-12-bTRWOB/gcc-12-12.2.0/debian/tmp-gcn/usr
    --enable-offload-defaulted --without-cuda-driver
    --enable-checking=release --build=x86_64-linux-gnu
    --host=x86_64-linux-gnu --target=x86_64-linux-gnu
    Thread model: posix
    Supported LTO compression algorithms: zlib zstd
    gcc version 12.2.0 (Debian 12.2.0-14)


    I will try with gcc-11
    * Origin: FPoint (2:221/6.600)
    --- SBBSecho 3.21-Linux
    * Origin: Dock Sud BBS - http://bbs.docksud.com.ar (4:902/26)
  • From Fernando Toledo@4:902/26 to Wilfred van Velzen on Tue Nov 12 20:26:17 2024
    El 12/11/24 a las 06:47, Wilfred van Velzen escribió:
    Hi Tommi,

    On 2024-11-12 10:38:07, you wrote to me:

    FT>>> I compiled it on debian12 with no errors (latests git from SF.net),
    WV>>
    WV>> I haven't tested it on any debian version yet...

    TK> Debian 11.11 here. Works.

    TK> gcc version 10.2.1 20210110 (Debian 10.2.1-6)

    Thanks for the information!


    Bye, Wilfred.

    --- FMail-lnx64 2.3.2.4-B20240523
    * Origin: FMail development HQ (2:280/464)


    @Tommi are you running latest git code?
    --- SBBSecho 3.21-Linux
    * Origin: Dock Sud BBS - http://bbs.docksud.com.ar (4:902/26)
  • From Wilfred van Velzen@2:280/464.112 to Fernando Toledo on Wed Nov 13 11:28:44 2024
    Hi Fernando,

    On 12 Nov 24 20:06, Fernando Toledo wrote to Wilfred van Velzen:
    about: "Re: fmail linux malloc(): invalid next size (unsorted)":

    Did you fill in a JAM MB name? Or (hudson) board number?

    I supose to use JAM no hudson..

    Yes, if you have the choice use JAM, hudson is very limited!

    Also I find the Write level (5706) rather strange...

    yes.. Maybe the fmail cmd corrupt the config settings after run it.

    Could be.

    I'm kind of thinking in the direction of a 32 vs 64 bit issue. I don't know if that can happen, but maybe you linked to the wrong system libraries?

    Wilfred.

    --- FMail-W64 2.3.2.3-B20240423
    * Origin: point@work (2:280/464.112)
  • From Tommi Koivula@2:221/6.600 to Fernando Toledo on Wed Nov 13 18:53:58 2024
    Hi Fernando.

    12 Nov 24 20:26, you wrote to Wilfred van Velzen:


    --- FMail-lnx64 2.3.2.4-B20240523
    * Origin: FMail development HQ (2:280/464)


    @Tommi are you running latest git code?

    Yes. However I'm one point behind Wilfred. ;)

    'Tommi

    --- FMail-lnx64 2.3.2.3-B20241113
    * Origin: FPoint (2:221/6.600)
  • From Wilfred van Velzen@2:280/464 to Tommi Koivula on Wed Nov 13 18:24:43 2024
    Hi Tommi,

    On 2024-11-13 18:53:58, you wrote to Fernando Toledo:

    --- FMail-lnx64 2.3.2.4-B20240523

    @Tommi are you running latest git code?

    Yes. However I'm one point behind Wilfred. ;)

    --- FMail-lnx64 2.3.2.3-B20241113

    That "change" is only on my HD, there is nothing committed yet.

    (Change: Only an extra #ifdef..#endif pair for the windows version)


    Bye, Wilfred.

    --- FMail-lnx64 2.3.2.4-B20240523
    * Origin: FMail development HQ (2:280/464)
  • From Wilfred van Velzen@2:280/464 to Tommi Koivula on Wed Nov 13 18:33:38 2024
    Hi Tommi,

    On 2024-11-13 18:53:58, you wrote to Fernando Toledo:

    --- FMail-lnx64 2.3.2.3-B20241113

    Btw: Have you tried the fmstats.py script yet? (branch json_toss_log)

    ;-)


    Bye, Wilfred.

    --- FMail-lnx64 2.3.2.4-B20240523
    * Origin: FMail development HQ (2:280/464)
  • From Tommi Koivula@2:221/6 to Wilfred van Velzen on Thu Nov 14 11:28:06 2024
    On 13.11.2024 17.33, Wilfred van Velzen wrote:


    On 2024-11-13 18:53:58, you wrote to Fernando Toledo:

    --- FMail-lnx64 2.3.2.3-B20241113

    Btw: Have you tried the fmstats.py script yet? (branch json_toss_log)

    Nope, not yet.

    'Tommi

    --- FMail-lnx64 2.3.2.3-B20241113
    * Origin: nntp://news.fidonet.fi (2:221/6.0)
  • From Wilfred van Velzen@2:280/464 to Tommi Koivula on Thu Nov 14 11:16:13 2024
    Hi Tommi,

    On 2024-11-14 11:28:06, you wrote to me:

    --- FMail-lnx64 2.3.2.3-B20241113

    Btw: Have you tried the fmstats.py script yet? (branch json_toss_log)

    Nope, not yet.

    That's a pity! ;-)


    Bye, Wilfred.

    --- FMail-lnx64 2.3.2.4-B20240523
    * Origin: FMail development HQ (2:280/464)
  • From Fernando Toledo@4:902/26 to Wilfred van Velzen on Fri Nov 15 00:10:20 2024
    El 13/11/24 a las 07:28, Wilfred van Velzen escribió:
    Hi Fernando,

    On 12 Nov 24 20:06, Fernando Toledo wrote to Wilfred van Velzen:
    about: "Re: fmail linux malloc(): invalid next size (unsorted)":

    >> Did you fill in a JAM MB name? Or (hudson) board number?
    >>
    FT> I supose to use JAM no hudson..

    Yes, if you have the choice use JAM, hudson is very limited!

    >> Also I find the Write level (5706) rather strange...

    FT> yes.. Maybe the fmail cmd corrupt the config settings after run it.

    Could be.

    I'm kind of thinking in the direction of a 32 vs 64 bit issue. I don't know if that can happen, but maybe you linked to the wrong system libraries?

    I build on 64bits system, I testing with relases builds from SF.net and
    have similar issue, after run "fmail toss" then fconfig area mgr won't
    load the area tag/name correctly
    I will try to get more debug details
    --- SBBSecho 3.22-Linux
    * Origin: Dock Sud BBS - http://bbs.docksud.com.ar (4:902/26)
  • From Wilfred van Velzen@2:280/464 to Fernando Toledo on Fri Nov 15 11:49:11 2024
    Hi Fernando,

    On 2024-11-15 00:10:20, you wrote to me:

    I'm kind of thinking in the direction of a 32 vs 64 bit issue. I don't
    know if that can happen, but maybe you linked to the wrong system
    libraries?

    I build on 64bits system, I testing with relases builds from SF.net and have similar issue, after run "fmail toss" then fconfig area mgr won't load the area tag/name correctly

    Interesting. So it seems to be something in your system, rather than the source/program. Because on other systems these precompiled programs don't have the same issues... But very strange.


    Bye, Wilfred.

    --- FMail-lnx64 2.3.2.4-B20240523
    * Origin: FMail development HQ (2:280/464)

Novedades:

Servidor de Quake 3 Arena Online! - Conectate a ferchobbs.ddns.net, puerto 27960 y vence con tu equipo!