From noreply-nasm at dev.nasm.us Tue Apr 6 03:04:10 2021 From: noreply-nasm at dev.nasm.us (noreply-nasm at dev.nasm.us) Date: Tue, 06 Apr 2021 10:04:10 +0000 Subject: [Nasm-bugs] [Bug 3392745] gmake golden produce different output on i386 and SPARC In-Reply-To: References: Message-ID: https://bugzilla.nasm.us/show_bug.cgi?id=3392745 Petr Sumbera changed: What |Removed |Added ---------------------------------------------------------------------------- Status|PENDING |OPEN Resolution|NEEDINFO |--- -- You are receiving this mail because: You are watching all bug changes. You are on the CC list for the bug. From noreply-nasm at dev.nasm.us Wed Apr 14 00:36:35 2021 From: noreply-nasm at dev.nasm.us (noreply-nasm at dev.nasm.us) Date: Wed, 14 Apr 2021 07:36:35 +0000 Subject: [Nasm-bugs] [Bug 3392748] New: A inifinite loop causing heap overflow, and a null pointer dereferencing Message-ID: https://bugzilla.nasm.us/show_bug.cgi?id=3392748 Bug ID: 3392748 Summary: A inifinite loop causing heap overflow, and a null pointer dereferencing Product: NASM Version: 2.16 (development) Hardware: All OS: Linux Status: OPEN Severity: normal Priority: Medium Component: Assembler Assignee: nobody at nasm.us Reporter: jasonliang30115 at gmail.com CC: chang.seok.bae at intel.com, gorcunov at gmail.com, hpa at zytor.com, nasm-bugs at nasm.us Obtained from: Built from git using configure Created attachment 411815 --> https://bugzilla.nasm.us/attachment.cgi?id=411815&action=edit This input will cause an infinite loop until nasm crash Here is detailed information environment (output of uname -a: Linux fc187431a65d 4.15.0-109-generic #110-Ubuntu SMP Tue Jun 23 02:39:32 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux version: NASM version 2.16rc0 problem: run nasm with the following command nasm -felf64 The `infinite_loop` input file provided will trigger a infinite loop, and the memory consumed will keep growing until a OOM is triggered. -- You are receiving this mail because: You are watching all bug changes. You are on the CC list for the bug. From noreply-nasm at dev.nasm.us Wed Apr 14 00:37:57 2021 From: noreply-nasm at dev.nasm.us (noreply-nasm at dev.nasm.us) Date: Wed, 14 Apr 2021 07:37:57 +0000 Subject: [Nasm-bugs] [Bug 3392748] A inifinite loop causing heap overflow, and a null pointer dereferencing In-Reply-To: References: Message-ID: https://bugzilla.nasm.us/show_bug.cgi?id=3392748 jason changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jasonliang30115 at gmail.com --- Comment #1 from jason --- Another input that will cause null pointer dereferencing cannot be attached as the submission system only allow me to upload one file, however I think the bug is pretty much the same. -- You are receiving this mail because: You are watching all bug changes. You are on the CC list for the bug. From noreply-nasm at dev.nasm.us Wed Apr 14 00:40:37 2021 From: noreply-nasm at dev.nasm.us (noreply-nasm at dev.nasm.us) Date: Wed, 14 Apr 2021 07:40:37 +0000 Subject: [Nasm-bugs] [Bug 3392748] A inifinite loop causing heap overflow, and a null pointer dereferencing In-Reply-To: References: Message-ID: https://bugzilla.nasm.us/show_bug.cgi?id=3392748 --- Comment #2 from jason --- Created attachment 411816 --> https://bugzilla.nasm.us/attachment.cgi?id=411816&action=edit This input will cause a null pointer dereferecing when executing `nasm -felf64 crash` -- You are receiving this mail because: You are on the CC list for the bug. You are watching all bug changes. From noreply-nasm at dev.nasm.us Thu Apr 15 21:05:19 2021 From: noreply-nasm at dev.nasm.us (noreply-nasm at dev.nasm.us) Date: Fri, 16 Apr 2021 04:05:19 +0000 Subject: [Nasm-bugs] [Bug 3392718] Intelligent sync mode seems to be non-functional In-Reply-To: References: Message-ID: https://bugzilla.nasm.us/show_bug.cgi?id=3392718 felix.von.s at posteo.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |felix.von.s at posteo.de --- Comment #1 from felix.von.s at posteo.de --- Created attachment 411817 --> https://bugzilla.nasm.us/attachment.cgi?id=411817&action=edit Patch for the problem A two-liner seems to be enough to fix this. I?m not even sure if the first line is necessary. -- You are receiving this mail because: You are watching all bug changes. You are on the CC list for the bug. From noreply-nasm at dev.nasm.us Mon Apr 19 22:38:09 2021 From: noreply-nasm at dev.nasm.us (noreply-nasm at dev.nasm.us) Date: Tue, 20 Apr 2021 05:38:09 +0000 Subject: [Nasm-bugs] [Bug 3392631] nasm generates broken .debug_loc section on ELF32 In-Reply-To: References: Message-ID: https://bugzilla.nasm.us/show_bug.cgi?id=3392631 Mike Hommey changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mh+anfz at glandium.org --- Comment #7 from Mike Hommey --- eb571a3ac387a721d52fdab448da7c8768bdaa18 moved the code that caused problems under a `if (0) {}`, so practically speaking, this bug is fixed, although the code is still there as is, and if it's ever restored, this will happen again. -- You are receiving this mail because: You are watching all bug changes. You are on the CC list for the bug.