Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 2304  |
|  Wilfred van Velzen to Fernando Toledo  |
|  Re: fmail linux malloc(): invalid next s  |
|  13 Nov 24 11:28:44  |
 RFC-X-No-Archive: Yes TZUTC: 0100 CHRS: CP437 2 PID: GED+W64 1.1.5-b20240306 MSGID: 2:280/464.112 67347fe5 REPLY: 396.fidonetfmailhel@4:902/26 2b9916f6 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? Wilfred. --- FMail-W64 2.3.2.3-B20240423 * Origin: point@work (2:280/464.112) SEEN-BY: 90/1 103/705 105/81 106/201 124/5016 128/187 129/305 153/757 SEEN-BY: 153/7715 154/10 30 203/0 218/700 221/0 226/30 227/114 229/110 SEEN-BY: 229/114 206 275 317 426 428 470 550 664 700 240/1120 5832 SEEN-BY: 266/512 280/464 5003 5006 5555 282/1038 291/111 292/854 8125 SEEN-BY: 301/1 310/31 320/219 322/757 341/66 234 342/200 396/45 423/120 SEEN-BY: 460/58 256 1124 467/888 633/280 712/848 770/1 902/26 5020/400 SEEN-BY: 5020/8912 5054/30 PATH: 280/464 460/58 229/426 |
[ << oldest | < older | list | newer > | newest >> ]