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),
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 ()
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:
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?
El 11/11/24 a las 18:38, Wilfred van Velzen 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!
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...
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:
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
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
malloc(): invalid next size (unsorted)
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)
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
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?
Also I find the Write level (5706) rather strange...
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
* Origin: FPoint (2:221/6.600)--- SBBSecho 3.21-Linux
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)
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.
--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)
@Tommi are you running latest git code?
--- 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
--- FMail-lnx64 2.3.2.3-B20241113
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)
--- FMail-lnx64 2.3.2.3-B20241113
Btw: Have you tried the fmstats.py script yet? (branch json_toss_log)
Nope, not yet.
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?
Sysop: | DaiTengu |
---|---|
Location: | Appleton, WI |
Users: | 993 |
Nodes: | 10 (0 / 10) |
Uptime: | 214:59:57 |
Calls: | 12,972 |
Files: | 186,574 |
Messages: | 3,268,553 |