daily CVS update output

2020-10-01 Thread NetBSD source update
Updating src tree: P src/doc/RESPONSIBLE cvs update: `src/doc/TODO.ptrace' is no longer in the repository cvs update: `src/doc/TODO.sanitizers' is no longer in the repository P src/external/mit/xorg/bin/xeyes/Makefile P src/share/man/man4/pms.4 P src/sys/arch/aarch64/aarch64/procfs_machdep.c P sr

Re: cannot allocate memory running mame

2020-10-01 Thread Thomas Klausner
On Thu, Oct 01, 2020 at 02:11:55PM +0200, Martin Husemann wrote: > On Thu, Oct 01, 2020 at 02:06:55PM +0200, Thomas Klausner wrote: > > Actually, that is the size of mame stripped, so yes, I need this bigger :) > > The unstripped code size should not be bigger, symbols are a separate > (non loadab

Re: cannot allocate memory running mame

2020-10-01 Thread Greg Troxel
Thomas Klausner writes: >> > /* >> > * Virtual memory related constants, all in bytes >> > */ >> > #define MAXTSIZ (256*1024*1024) /* max text size */ >> >> AFAICT for amd64 the limit is arbitrary, if you only need it temporarily for >> debugging purposes, just bump it to 512

Re: cannot allocate memory running mame

2020-10-01 Thread Martin Husemann
On Thu, Oct 01, 2020 at 02:06:55PM +0200, Thomas Klausner wrote: > Actually, that is the size of mame stripped, so yes, I need this bigger :) The unstripped code size should not be bigger, symbols are a separate (non loadable) section. > Should we bump it in general? Don't think so (but also don

Re: cannot allocate memory running mame

2020-10-01 Thread Thomas Klausner
On Thu, Oct 01, 2020 at 02:05:52PM +0200, Martin Husemann wrote: > On Thu, Oct 01, 2020 at 02:03:30PM +0200, Martin Husemann wrote: > > On Thu, Oct 01, 2020 at 01:56:15PM +0200, Thomas Klausner wrote: > > > Program Headers: > > > Type Offset VirtAddr PhysAddr > > >

Re: cannot allocate memory running mame

2020-10-01 Thread Martin Husemann
On Thu, Oct 01, 2020 at 02:03:30PM +0200, Martin Husemann wrote: > On Thu, Oct 01, 2020 at 01:56:15PM +0200, Thomas Klausner wrote: > > Program Headers: > > Type Offset VirtAddr PhysAddr > > FileSizMemSiz Flags Align > [..

Re: cannot allocate memory running mame

2020-10-01 Thread Martin Husemann
On Thu, Oct 01, 2020 at 01:56:15PM +0200, Thomas Klausner wrote: > Program Headers: > Type Offset VirtAddr PhysAddr > FileSizMemSiz Flags Align [..] > LOAD 0x 0x0040 0x004000

Re: cannot allocate memory running mame

2020-10-01 Thread Thomas Klausner
On Thu, Oct 01, 2020 at 01:55:20PM +0200, Martin Husemann wrote: > On Thu, Oct 01, 2020 at 01:27:38PM +0200, Thomas Klausner wrote: > > but that was not sufficient. > > > > > du -sh /usr/pkg/bin/mame > > 269M/usr/pkg/bin/mame > > that is .. big. > > Can you show readelf -l output for the bin

Re: cannot allocate memory running mame

2020-10-01 Thread Martin Husemann
On Thu, Oct 01, 2020 at 01:27:38PM +0200, Thomas Klausner wrote: > but that was not sufficient. > > > du -sh /usr/pkg/bin/mame > 269M/usr/pkg/bin/mame that is .. big. Can you show readelf -l output for the binary? Martin

cannot allocate memory running mame

2020-10-01 Thread Thomas Klausner
Hi! After updating mame (with debugging symbols) to 0.225 on -current, I see: > mame zsh: cannot allocate memory: mame I've increased the ulimits to: > ulimit -a -t: cpu time (seconds) unlimited -f: file size (blocks) unlimited -d: data seg size (kbytes) 83886