[pcre-dev] [Bug 1672] PCRE Library Heap Overflow in compile_…

Startseite
Nachricht löschen
Autor: admin
Datum:  
To: pcre-dev
Alte Treads: [pcre-dev] [Bug 1672] New: PCRE Library Heap Overflow in compile_regex()
Betreff: [pcre-dev] [Bug 1672] PCRE Library Heap Overflow in compile_regex()
https://bugs.exim.org/show_bug.cgi?id=1672

Mehmet gelisin <mehmetgelisin@???> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mehmetgelisin@???


--- Comment #2 from Mehmet gelisin <mehmetgelisin@???> ---
Dear PCRE2 Team,
http://www-look-4.com/
If have a question regarding the direct calls to mmap/VirtualAlloc in, e.g.
sljit_allocate_stack. http://www.iu-bloomington.com/ It is not very clear to me
why they are needed, as a user supplied allocator is available.
https://www.webb-dev.co.uk/
In my environment, where everything is in shared memory, the current approach
doesn't work. https://waytowhatsnext.com/

I changed the coding locally to just call SLJIT_MALLOC and everything works
just as fine. Also 500k http://www.acpirateradio.co.uk/ are not that much
memory in 2020 for a normal memory allocator. No need to bother the operating
system. http://www.logoarts.co.uk/

All the logic simplifies considerably and even the whole "page size" stuff is
not really needed. http://www.slipstone.co.uk/

Would it be possible to include this via a compile time flag? I could even try
to share my coding.

Best regards, http://embermanchester.uk/

Dear PCRE2 Team,

If have a question regarding the direct calls to mmap/VirtualAlloc in, e.g.
sljit_allocate_stack. It is not very clear to me why they are needed, as a user
supplied allocator is available. http://connstr.net/

In my environment, where everything is in shared memory, the current approach
doesn't work.
http://joerg.li/
I changed the coding locally to just call SLJIT_MALLOC and everything works
just as fine. Also 500k are not that much memory in 2020 for a normal memory
allocator. No need to bother the operating system.

All the logic simplifies considerably and even the whole "page size" stuff is
not really needed. http://www.jopspeech.com/

Would it be possible to include this via a compile time flag? I could even try
to share my coding.

Best regards,

Dear PCRE2 Team,

If have a question regarding the direct calls to mmap/VirtualAlloc in, e.g.
sljit_allocate_stack. It is not very clear to me why they are needed, as a user
supplied allocator is available. http://www.wearelondonmade.com/

In my environment, where everything is in shared memory, the current approach
doesn't work.

I changed the coding locally to just call SLJIT_MALLOC and everything works
just as fine. Also 500k are not that much memory in 2020 for a normal memory
allocator. No need to bother the operating system. http://www.compilatori.com/

All the logic simplifies considerably and even the whole "page size" stuff is
not really needed.

Would it be possible to include this via a compile time flag? I could even try
to share my coding.

Best regards,

--
You are receiving this mail because:
You are on the CC list for the bug.