[Slackbuilds-users] malloc runtime error, any suggestions?

[phalange at komputermatrix.com]

It's version 3.5.1 -- it's pushed but not distributed yet.

Xorg doesn't offer much:

X.Org X Server 1.20.14
X Protocol Version 11, Revision 0
Build Operating System: Slackware 15.0 Slackware Linux Project
Current Operating System: Linux slack-t470s.localdomain 5.15.145 #1 SMP 
PREEMPT Sun Dec 24 00:07:06 CST 2023 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-huge-5.15.145 
root=/dev/mapper/slackvg-slackware ro
Build Date: 03 April 2024  05:19:08PM

Current version of pixman: 0.40.0
         Before reporting problems, check http://wiki.x.org
         to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
         (++) from command line, (!!) notice, (II) informational,
         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Apr 15 21:28:05 2024
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
spectrwm: Welcome to spectrwm V3.5.1 Build: 3.5.1
malloc(): invalid size (unsorted)
xinit: connection to X server lost

waiting for X server to shut down (II) Server terminated successfully 
(0). Closing log file.



On 2024-04-15 17:37, B. Watson wrote:
> On Mon, 15 Apr 2024, phalange at komputermatrix.com wrote:
> 
>> Hi all, I'm getting a malloc() runtime error startx-ing a window 
>> manager called spectrwm.
>> 
>> Any suggestions on how to get more details on this? It seems this 
>> version of spectrwm runs on other distros, like Alpine for example.
>> 
>> I'd like to report it to the developer if it's really a bug, or patch 
>> it in Slackware.
> 
> It builds and runs fine here.
> 
> Can you give us more detail? Try 'startx &> ~/x.log', and attach the
> resulting x.log to a list email...
> 
> Also, are you on Slackware 15.0? Slackware-current isn't officially
> supported, but if it's a problem with -current, we'd like to know.
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/