issue_owner_repo listlengths 2 2 | issue_body stringlengths 0 261k ⌀ | issue_title stringlengths 1 925 | issue_comments_url stringlengths 56 81 | issue_comments_count int64 0 2.5k | issue_created_at stringlengths 20 20 | issue_updated_at stringlengths 20 20 | issue_html_url stringlengths 37 62 | issue_github_id int64 387k 2.46B | issue_number int64 1 127k |
|---|---|---|---|---|---|---|---|---|---|
[
"WebAssembly",
"wabt"
] | here is my test code
```
(module
(func (result i32)
(i32.add (i32.const 624485) (i32.const 2))))
```
LEB of 624485 [should be 0xE58E26](https://en.wikipedia.org/wiki/LEB128#Unsigned_LEB128)
But from the prototype if get
```
; function 0
....
0000014: 0a ; OPCODE_I32_C... | LEB128 question | https://api.github.com/repos/WebAssembly/wabt/issues/8/comments | 4 | 2015-11-20T19:13:34Z | 2015-11-20T21:45:05Z | https://github.com/WebAssembly/wabt/issues/8 | 118,107,165 | 8 |
[
"WebAssembly",
"wabt"
] | I have a test that generated the following code, and fed it into sexpr-wasm
(module
(func $foomore(call $foo (i32.const 0x0)) )
(func $foo (param i32)(nop))
)
Note the lack of space between $foomore and its opening paren. Sometime between rev 64fb062d and rev 7601228b this stopped being accepted by the parser, whi... | Whitespace between function name token and left paren | https://api.github.com/repos/WebAssembly/wabt/issues/6/comments | 2 | 2015-10-13T19:28:18Z | 2015-10-14T00:28:29Z | https://github.com/WebAssembly/wabt/issues/6 | 111,252,358 | 6 |
[
"WebAssembly",
"wabt"
] | The spec interpreter reports assertion errors with line numbers from the source. This would be really handy for debugging codegen issues (e.g. in a test suite with hundreds of assertions, which one is failing?). Currently WAOT just tracks and prints the count (i.e. "assertion number X failed") but a line number would b... | Provide a way to get SourceLocations | https://api.github.com/repos/WebAssembly/wabt/issues/4/comments | 4 | 2015-10-10T22:46:12Z | 2015-10-19T07:30:00Z | https://github.com/WebAssembly/wabt/issues/4 | 110,821,326 | 4 |
[
"yasm",
"yasm"
] | I have the following snippet in my code, with the idea of creating a compilation error if an impossible set of defines are set:
```
%if LABEL && ALTLABEL
%error cant have LABEL and ALTLABEL together
%endif
```
In nasm this behaves as expected. In yasm I get the message, but then yasm returns with exit code 0, wit... | %error macro only leads to a warning/different behaviour than nasm | https://api.github.com/repos/yasm/yasm/issues/278/comments | 0 | 2024-06-27T12:15:32Z | 2024-06-27T12:15:32Z | https://github.com/yasm/yasm/issues/278 | 2,377,998,112 | 278 |
[
"yasm",
"yasm"
] | Hi, developers.
I have detected an access violation at `nasm-pp.c:4765:21` in the latest commit version 9defefa.
### System
I discover this crash with a docker container configured with 1 CPU core of Intel(R) Xeon(R) Gold 5218R CPU @ 2.10GHz and the 64-bit Ubuntu 18.04 LTS.
### Version
`9defefa`
### P... | null-pointer-dereference at nasm-pp.c:4765:21 (9defefa) | https://api.github.com/repos/yasm/yasm/issues/277/comments | 0 | 2024-06-12T13:52:01Z | 2024-06-12T13:52:01Z | https://github.com/yasm/yasm/issues/277 | 2,348,837,907 | 277 |
[
"yasm",
"yasm"
] | Hi, developers.
I have detected a heap-buffer-overflow crash at `nasm-pp.c:3902:34` in the latest commit version 9defefa.
### System
I discover this crash with a docker container configured with 1 CPU core of Intel(R) Xeon(R) Gold 5218R CPU @ 2.10GHz and the 64-bit Ubuntu 18.04 LTS.
### Version
`9defefa`... | heap-buffer-overflow at nasm-pp.c:3902:34 (9defefa) | https://api.github.com/repos/yasm/yasm/issues/276/comments | 0 | 2024-06-09T14:09:52Z | 2024-06-09T14:09:52Z | https://github.com/yasm/yasm/issues/276 | 2,342,277,934 | 276 |
[
"yasm",
"yasm"
] | Hi, developers.
I have detected a heap-use-after-free crash at nasm-pp.c:5025:39 in the latest commit version 9defefa.
### System
I discover this crash with a docker container configured with 1 CPU core of Intel(R) Xeon(R) Gold 5218R CPU @ 2.10GHz and the 64-bit Ubuntu 18.04 LTS.
### Version
`9defefa`
... | heap-use-after-free at nasm-pp.c:5025:39 (9defefa) | https://api.github.com/repos/yasm/yasm/issues/275/comments | 0 | 2024-06-09T13:53:49Z | 2024-06-09T13:53:49Z | https://github.com/yasm/yasm/issues/275 | 2,342,271,158 | 275 |
[
"yasm",
"yasm"
] | Hi, developers.
I have detected a heap-use-after-free crash at nasm-pp.c:3879:33 in the latest commit version 9defefa.
### System
I discover this crash with a docker container configured with 1 CPU core of Intel(R) Xeon(R) Gold 5218R CPU @ 2.10GHz and the 64-bit Ubuntu 18.04 LTS.
### Version
`9defefa`
... | heap-use-after-free at nasm-pp.c:3879:33 (9defefa) | https://api.github.com/repos/yasm/yasm/issues/274/comments | 0 | 2024-06-09T13:33:28Z | 2024-06-09T13:33:28Z | https://github.com/yasm/yasm/issues/274 | 2,342,254,357 | 274 |
[
"yasm",
"yasm"
] | Hi, developers.
I have detected an access violation at nasm-pp.c:3816:17 in the latest commit version 9defefa.
### System
I discover this crash with a docker container configured with 1 CPU core of Intel(R) Xeon(R) Gold 5218R CPU @ 2.10GHz and the 64-bit Ubuntu 18.04 LTS.
### Version
`9defefa`
### Pro... | null-pointer-dereference at nasm-pp.c:3816:17 (9defefa) | https://api.github.com/repos/yasm/yasm/issues/273/comments | 0 | 2024-06-09T13:03:28Z | 2024-06-12T13:52:42Z | https://github.com/yasm/yasm/issues/273 | 2,342,239,708 | 273 |
[
"yasm",
"yasm"
] | When running the test suite of 9defefa on Fedora rawhide (gcc-14.0.1, binutils-2.42.50), I'm getting the following test failure on x86 32-bit (i686) arch:
```
$ cat test-suite.log
==================================
yasm 1.3.0: ./test-suite.log
==================================
# TOTAL: 44
# PASS: 43
# S... | macho64_test failure on x86 32-bit | https://api.github.com/repos/yasm/yasm/issues/270/comments | 0 | 2024-03-22T10:37:20Z | 2024-03-22T10:37:20Z | https://github.com/yasm/yasm/issues/270 | 2,202,199,029 | 270 |
[
"yasm",
"yasm"
] | When building latest git HEAD (9defefa), the test suite (`make check`) fails randomly if run in parallel with `make -jN`.
| test suite fails randomly with parallel make | https://api.github.com/repos/yasm/yasm/issues/269/comments | 0 | 2024-03-22T09:52:09Z | 2024-03-22T09:52:09Z | https://github.com/yasm/yasm/issues/269 | 2,202,113,166 | 269 |
[
"yasm",
"yasm"
] | Hello, I am a graduate student specializing in static analysis of programs. Recently, while using a static analysis tool to detect issues in open-source projects, I found several defects in the project. The description of the defects can be found at the following link:https://github.com/LuMingYinDetect/yasm_defects/blo... | The vulnerability is a memory leak bug located at line 71 of the file /yasm/tools/genmacro/genmacro.c | https://api.github.com/repos/yasm/yasm/issues/268/comments | 0 | 2024-02-28T07:39:04Z | 2024-02-28T07:39:04Z | https://github.com/yasm/yasm/issues/268 | 2,158,309,795 | 268 |
[
"yasm",
"yasm"
] | Hello, I am a graduate student specializing in static analysis of programs. Recently, while using a static analysis tool to detect issues in open-source projects, I found several defects in the project. The description of the defects can be found at the following link:https://github.com/LuMingYinDetect/yasm_defects/blo... | The defect occurs at line 177 in the file /yasm/modules/preprocs/nasm/nasmlib.c | https://api.github.com/repos/yasm/yasm/issues/267/comments | 0 | 2024-02-28T07:38:26Z | 2024-02-28T07:38:26Z | https://github.com/yasm/yasm/issues/267 | 2,158,308,867 | 267 |
[
"yasm",
"yasm"
] | #### Description:
~~~shell
AddressSanitizer: heap-use-after-free /mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-master/libyasm/expr.c:1116:20 in expr_traverse_nodes_post
~~~
#### Project:
<https://github.com/yasm/yasm>
#### Version:
~~~bash
fk@localhost:/mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-mast... | heap-use-after-free in /libyasm/expr.c:1116:20 in expr_traverse_nodes_post | https://api.github.com/repos/yasm/yasm/issues/262/comments | 0 | 2024-01-25T12:49:49Z | 2024-01-25T12:57:12Z | https://github.com/yasm/yasm/issues/262 | 2,100,327,671 | 262 |
[
"yasm",
"yasm"
] | #### Description:
~~~shell
AddressSanitizer: SEGV /mnt/c/Users/Orrr/Desktop/Fuzz/yasm-master/yasm-master/modules/preprocs/nasm/nasm-pp.c:3862:20 in expand_mmac_params
==27727==ABORTING
~~~
#### Project:
<https://github.com/yasm/yasm>
#### Version:
~~~bash
fk@localhost:/mnt/c/Users/Orrr/Desktop/Fuzz/yasm-ma... | SEGV in /modules/preprocs/nasm/nasm-pp.c:3862:20 in expand_mmac_params | https://api.github.com/repos/yasm/yasm/issues/261/comments | 0 | 2024-01-25T12:31:25Z | 2024-01-25T12:55:28Z | https://github.com/yasm/yasm/issues/261 | 2,100,296,161 | 261 |
[
"yasm",
"yasm"
] | I might be asking this in the wrong place, but after creating an installer using this tool, how do I get the newly created installer to run silently without any user interaction? | Which flag allows for silent installation? | https://api.github.com/repos/yasm/yasm/issues/260/comments | 0 | 2024-01-24T00:41:38Z | 2024-01-24T00:41:38Z | https://github.com/yasm/yasm/issues/260 | 2,097,210,152 | 260 |
[
"yasm",
"yasm"
] | My compile script:
```
git clone https://github.com/yasm/yasm.git
cd yasm
./autogen.sh
./configure \
--host=x86_64-w64-mingw32 \
--target=x86_64-w64-mingw32 \
--prefix=target
make
make install
```
error as below:
```
I am going to run ./configure with --enable-maintainer-mode
If you wish to pass ... | configure error when cross-compile on linux | https://api.github.com/repos/yasm/yasm/issues/258/comments | 0 | 2024-01-19T04:05:11Z | 2024-01-19T04:05:11Z | https://github.com/yasm/yasm/issues/258 | 2,089,531,385 | 258 |
[
"yasm",
"yasm"
] | ### 1.version:
yasm v1.3.0
### 2.test environment
ubuntu 18.04 TLS
### 3.build yasm with asan
$ export CC=/usr/bin/clang
$ export CXX=/usr/bin/clang++
$ ./configure --disable-shared CFLAGS="-fsanitize-recover=address -ggdb" CXXFLAGS="-fsanitize=address -ggdb"
$ make
### 4 run it
../yasm -w poc
### 5... | Memory leak vulnerability discovered | https://api.github.com/repos/yasm/yasm/issues/257/comments | 2 | 2023-12-28T02:06:30Z | 2024-01-19T15:26:39Z | https://github.com/yasm/yasm/issues/257 | 2,057,907,048 | 257 |
[
"yasm",
"yasm"
] | # project
https://github.com/yasm/yasm
Commit: 9defefa
# os info
Ubuntu18.04 TLS
# poc
[poc.zip](https://github.com/yasm/yasm/files/13631095/poc.zip)
# build
./autogen.sh
make distclean
CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-poi... | heap-use-after-free yasm/libyasm/expr.c:1116 in expr_traverse_nodes_post | https://api.github.com/repos/yasm/yasm/issues/256/comments | 0 | 2023-12-11T04:53:37Z | 2024-01-11T10:53:28Z | https://github.com/yasm/yasm/issues/256 | 2,034,827,460 | 256 |
[
"yasm",
"yasm"
] | This seems to appear every time I pass `-Werror` to yasm. It not only seems redundant, but it also makes it harder to visually identify any actual errors. What's the intention of this message? Is it possible to suppress it? `nasm` doesn't seem to print this. | `error: warnings being treated as errors` | https://api.github.com/repos/yasm/yasm/issues/255/comments | 3 | 2023-12-07T20:08:57Z | 2023-12-07T20:35:57Z | https://github.com/yasm/yasm/issues/255 | 2,031,444,525 | 255 |
[
"yasm",
"yasm"
] | In nasm `mov a, [foo wrt ..got]` (or `..gotpc`?) creates a GOTPCREL relocation, but yasm specifies this as `mov a, [foo wrt ..gotpcrel]`. Is the syntax difference intentional? | x86-64 GOTPCREL wrt syntax doesn't match nasm | https://api.github.com/repos/yasm/yasm/issues/254/comments | 1 | 2023-11-30T21:57:02Z | 2023-11-30T22:28:23Z | https://github.com/yasm/yasm/issues/254 | 2,019,576,075 | 254 |
[
"yasm",
"yasm"
] | **The name of an affected Product**
[yasm](https://github.com/yasm/yasm)
**The affected version**
Commit: [9defefa](https://github.com/yasm/yasm/commit/9defefae9fbcb6958cddbfa778c1ea8605da8b8b)
yasm 1.3.0.86.g9def
**Description**
An issue in yasm 1.3.0.86.g9def allows a attacker to cause a denial of service v... | SEGV in yasm_section_bcs_first() at libyasm/section.c:619 | https://api.github.com/repos/yasm/yasm/issues/253/comments | 1 | 2023-11-26T08:48:59Z | 2024-01-03T11:22:18Z | https://github.com/yasm/yasm/issues/253 | 2,010,956,429 | 253 |
[
"yasm",
"yasm"
] | **The name of an affected Product**
[yasm](https://github.com/yasm/yasm)
**The affected version**
Commit: [9defefa](https://github.com/yasm/yasm/commit/9defefae9fbcb6958cddbfa778c1ea8605da8b8b)
yasm 1.3.0.86.g9def
**Description**
An issue in yasm 1.3.0.86.g9def allows a attacker to cause a denial of service v... | SEGV in the function expand_mmac_params() at modules/preprocs/nasm/nasm-pp.c:4013 | https://api.github.com/repos/yasm/yasm/issues/252/comments | 3 | 2023-11-26T04:38:16Z | 2024-03-23T09:32:24Z | https://github.com/yasm/yasm/issues/252 | 2,010,889,074 | 252 |
[
"yasm",
"yasm"
] | I enabled "generate debug information: Yes (-g cv8)", breakpoints do not work in asm file.
Used this to install yasm in VS2017:
https://github.com/ShiftMediaProject/VSYASM
asm file:
```
section .text
global _my_as... | Does yasm integrated in VS2017 support breakpoint in mixed cpp and asm file? | https://api.github.com/repos/yasm/yasm/issues/251/comments | 0 | 2023-11-24T12:15:58Z | 2023-11-24T12:15:58Z | https://github.com/yasm/yasm/issues/251 | 2,009,632,297 | 251 |
[
"yasm",
"yasm"
] | **The name of an affected Product**
[yasm](https://github.com/yasm/yasm)
**The affected version**
Commit: [9defefa](https://github.com/yasm/yasm/commit/9defefae9fbcb6958cddbfa778c1ea8605da8b8b)
yasm 1.3.0.86.g9def
**Description**
An issue in yasm 1.3.0.86.g9def allows a attacker to cause a denial of service v... | heap-buffer-overflow in the function expr_delete_term() at libyasm/expr.c:1019 | https://api.github.com/repos/yasm/yasm/issues/250/comments | 1 | 2023-11-20T14:26:40Z | 2024-02-12T16:51:53Z | https://github.com/yasm/yasm/issues/250 | 2,002,324,400 | 250 |
[
"yasm",
"yasm"
] | **The name of an affected Product**
[yasm](https://github.com/yasm/yasm)
**The affected version**
Commit: [9defefa](https://github.com/yasm/yasm/commit/9defefae9fbcb6958cddbfa778c1ea8605da8b8b)
yasm 1.3.0.86.g9def
**Description**
An issue in yasm 1.3.0.86.g9def allows a attacker to cause a denial of service v... | heap-use-after-free in the function do_directive() at modules/preprocs/nasm/nasm-pp.c:2389 | https://api.github.com/repos/yasm/yasm/issues/249/comments | 0 | 2023-11-20T14:16:57Z | 2024-01-03T11:22:46Z | https://github.com/yasm/yasm/issues/249 | 2,002,305,193 | 249 |
[
"yasm",
"yasm"
] | **The name of an affected Product**
[yasm](https://github.com/yasm/yasm)
**The affected version**
Commit: [9defefa](https://github.com/yasm/yasm/commit/9defefae9fbcb6958cddbfa778c1ea8605da8b8b)
yasm 1.3.0.86.g9def
**Description**
An issue in yasm 1.3.0.86.g9def allows a attacker to cause a denial of service v... | SEGV in the function expand_smacro() at modules/preprocs/nasm/nasm-pp.c:4357 | https://api.github.com/repos/yasm/yasm/issues/248/comments | 2 | 2023-11-20T14:03:30Z | 2024-01-04T10:06:59Z | https://github.com/yasm/yasm/issues/248 | 2,002,278,782 | 248 |
[
"yasm",
"yasm"
] | Hi, we found a null pointer dereference bug in the latest version of yasm.
### ASAN
```
==55571==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000048 (pc 0x000000577e9b bp 0x7fffe279e490 sp 0x7fffe279e290 T0)
==55571==The signal is caused by a READ memory access.
==55571==Hint: address points to the zer... | NULL Pointer Dereference in yasm_section_bcs_append at section.c:634 | https://api.github.com/repos/yasm/yasm/issues/247/comments | 0 | 2023-10-28T15:11:35Z | 2023-10-28T15:11:35Z | https://github.com/yasm/yasm/issues/247 | 1,966,632,045 | 247 |
[
"yasm",
"yasm"
] | Hi, we found memory leaks in the latest version of yasm.
### ASAN
```
==42150==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 56 byte(s) in 1 object(s) allocated from:
#0 0x4ac0a0 in malloc /root/build/llvm_tools/llvm-11.0.0.src/projects/compiler-rt/lib/asan/asan_malloc_linux.cpp:145
#1 0x58... | Memory leaks found. | https://api.github.com/repos/yasm/yasm/issues/246/comments | 0 | 2023-10-27T15:54:57Z | 2023-10-27T15:54:57Z | https://github.com/yasm/yasm/issues/246 | 1,965,795,866 | 246 |
[
"yasm",
"yasm"
] | hi!
* i am looking for some alternate to the Turbo Assembled (tasm)
* for doing the practical for the subject of MicroProcessors 8086 (so, i want to see the value of registers, flags, segments etc)
* using VSCodium or some dedicated IDE.
I found yasm via [alternativeto][yasm-alt2] & i have read the [yasm-site] ... | differences from nasm and which one to use? | https://api.github.com/repos/yasm/yasm/issues/245/comments | 1 | 2023-10-26T13:38:23Z | 2024-02-03T21:27:48Z | https://github.com/yasm/yasm/issues/245 | 1,963,603,855 | 245 |
[
"yasm",
"yasm"
] | The 1.3.0 release provides [yasm-1.3.0-win64.exe](http://www.tortall.net/projects/yasm/releases/yasm-1.3.0-win64.exe), which needs `MSVCRT100.dll`.
However, this dll is not installed by default on the Windows-2022 Github runners.
So it would be useful to, when a next release is done, to provide binaries that don't ne... | Provide MSVC runtime-free binary releases | https://api.github.com/repos/yasm/yasm/issues/240/comments | 0 | 2023-09-04T21:57:38Z | 2023-09-04T21:57:38Z | https://github.com/yasm/yasm/issues/240 | 1,880,901,969 | 240 |
[
"yasm",
"yasm"
] | Hello Yasm developers,
We recently conducted a fuzzing test on yasm and discovered an UAF bug. We would like to provide a detailed description of the bug and seek your assistance in addressing it.
version:
Yasm: 1.3.0
gcc:gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1)
ubuntu: 20.04
command to reproduce:
y... | heap-use-after-free libyasm/floatnum.c:509 in yasm_floatnum_destroy | https://api.github.com/repos/yasm/yasm/issues/237/comments | 0 | 2023-07-15T11:28:23Z | 2023-07-15T11:28:23Z | https://github.com/yasm/yasm/issues/237 | 1,806,028,408 | 237 |
[
"yasm",
"yasm"
] | Hello Yasm developers,
We recently conducted a fuzzing test on yasm and discovered a heap-buffer-overflow bug. We would like to provide a detailed description of the bug and seek your assistance in addressing it.
version:
Yasm: 1.3.0
gcc:gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1)
ubuntu: 20.04
command ... | heap-buffer-overflow modules/preprocs/nasm/nasm-pp.c:3977 in expand_mmac_params | https://api.github.com/repos/yasm/yasm/issues/236/comments | 0 | 2023-07-15T11:24:36Z | 2023-07-15T11:24:36Z | https://github.com/yasm/yasm/issues/236 | 1,806,027,134 | 236 |
[
"yasm",
"yasm"
] | The current latest tag, even it release on 2019, it was created in 2014.
The repo still active. (commit from 2 weeks ago).
Can you release new version? | Release new version | https://api.github.com/repos/yasm/yasm/issues/235/comments | 2 | 2023-07-12T00:10:54Z | 2023-12-12T20:08:11Z | https://github.com/yasm/yasm/issues/235 | 1,799,944,329 | 235 |
[
"yasm",
"yasm"
] | # Description
While fuzzing yasm, a SEGV occured which was positioned in yasm/libyasm/intnum.c:399:19 in yasm_intnum_copy.
This bug may allow attackers to cause a crash or denial of service via a designed crafted files.
# Operating system
Ubuntu 20.04.6 LTS
# ASAN info
```
./bin/yasm -p gas -f elf32 -g dwarf2 .... | SEGV in yasm/libyasm/intnum.c's function :yasm_intnum_copy | https://api.github.com/repos/yasm/yasm/issues/233/comments | 0 | 2023-06-29T13:07:01Z | 2023-06-30T15:08:56Z | https://github.com/yasm/yasm/issues/233 | 1,780,786,529 | 233 |
[
"yasm",
"yasm"
] | It seems that yasm's `-l` (listing) option does not include bytes for a `rep` prefix if the `rep` is on the same line as the affected `stos`.
## Steps to reproduce
Create `hello.S`:
```
.code64
rep ; stosq
```
Run:
```
$ yasm -p gas -L nasm -l hello.list hello.S
```
## Observed output
`hello.list`:
... | listing omits bytes of 'rep' prefix if on same line | https://api.github.com/repos/yasm/yasm/issues/230/comments | 0 | 2023-05-31T01:39:05Z | 2023-05-31T01:39:05Z | https://github.com/yasm/yasm/issues/230 | 1,733,245,762 | 230 |
[
"yasm",
"yasm"
] | cd tools/python-yasm/
python3 setup.py build
Traceback (most recent call last):
File "setup.py", line 81, in <module>
opts = ReadSetup("python-setup.txt")
File "setup.py", line 36, in ReadSetup
return dict(line.split('=', 1) for line in open(filename))
FileNotFoundError: [Errno 2] No such file or d... | missing python-setup.txt | https://api.github.com/repos/yasm/yasm/issues/229/comments | 0 | 2023-05-28T01:55:48Z | 2023-05-28T01:55:48Z | https://github.com/yasm/yasm/issues/229 | 1,729,082,792 | 229 |
[
"yasm",
"yasm"
] | # At first, I have built yasm:
installdir=/usr/local
git clone yasm
mkdir mybuild && cd mybuild
cmake -DCMAKE_INSTALL_PREFIX="$installdir" ..
make
ctest # No tests were found!!!
make install
cd ..
yasm --version # yasm-1.3.0
# to build x86 plugin - ok:
pushd plugins/x86
mkdir mybuild
cd m... | plugins build error | https://api.github.com/repos/yasm/yasm/issues/228/comments | 0 | 2023-05-28T01:26:34Z | 2023-05-28T01:26:34Z | https://github.com/yasm/yasm/issues/228 | 1,729,070,374 | 228 |
[
"yasm",
"yasm"
] | # There exists SEGV in yasm/modules/preprocs/nasm/nasm-pp.c:3570 in do_directive
## asan info:
```
AddressSanitizer:DEADLYSIGNAL
=================================================================
==1433063==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x55736a1a1cff bp 0x7fff4d5cbf50 sp 0x7ff... | There exists SEGV in yasm/modules/preprocs/nasm/nasm-pp.c:3570 in do_directive | https://api.github.com/repos/yasm/yasm/issues/222/comments | 1 | 2023-04-17T16:48:59Z | 2024-03-22T11:50:46Z | https://github.com/yasm/yasm/issues/222 | 1,671,589,854 | 222 |
[
"yasm",
"yasm"
] | # There exists heap-use-after-free in yasm/modules/preprocs/nasm/nasm-pp.c:3878 in expand_mmac_params
## asan info:
```
==708699==ERROR: AddressSanitizer: heap-use-after-free on address 0x60e0000012a8 at pc 0x55647c385147 bp 0x7ffe09f5d870 sp 0x7ffe09f5d860
READ of size 8 at 0x60e0000012a8 thread T0
#0 0x556... | There exists heap-use-after-free in yasm/modules/preprocs/nasm/nasm-pp.c:3878 in expand_mmac_params | https://api.github.com/repos/yasm/yasm/issues/221/comments | 1 | 2023-04-17T16:39:42Z | 2024-03-22T11:51:42Z | https://github.com/yasm/yasm/issues/221 | 1,671,576,475 | 221 |
[
"yasm",
"yasm"
] | # There exists SEGV in yasm/modules/preprocs/nasm/nasm-pp.c:4008 in expand_mmac_params
## asan info:
```
AddressSanitizer:DEADLYSIGNAL
=================================================================
==3645333==ERROR: AddressSanitizer: SEGV on unknown address 0x60bcf518f500 (pc 0x562c742f3049 bp 0x7ffc6fb07330 ... | There exists SEGV in yasm/modules/preprocs/nasm/nasm-pp.c:4008 in expand_mmac_params | https://api.github.com/repos/yasm/yasm/issues/220/comments | 1 | 2023-04-17T16:18:19Z | 2024-03-22T11:52:08Z | https://github.com/yasm/yasm/issues/220 | 1,671,545,980 | 220 |
[
"yasm",
"yasm"
] | # There exists SEGV in yasm/modules/preprocs/nasm/nasm-pp.c:2134/if_condition
## ASAN info:
```
AddressSanitizer:DEADLYSIGNAL
=================================================================
==2586705==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x56354074e373 bp 0x7ffcc98771d0 sp 0x7f... | There exists SEGV in yasm/modules/preprocs/nasm/nasm-pp.c:2134/if_condition | https://api.github.com/repos/yasm/yasm/issues/219/comments | 0 | 2023-04-17T14:00:21Z | 2023-04-18T03:20:34Z | https://github.com/yasm/yasm/issues/219 | 1,671,254,497 | 219 |
[
"yasm",
"yasm"
] | # stack-overflow yasm/modules/parsers/nasm/nasm-parse.c:1303 in parse_expr5
## project address
https://github.com/yasm/yasm
## info
OS：Ubuntu20.04 TLS
Build: ./autogen.sh && make distclean && CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-fram... | stack-overflow yasm/modules/parsers/nasm/nasm-parse.c:1303 in parse_expr5 | https://api.github.com/repos/yasm/yasm/issues/218/comments | 1 | 2023-03-31T08:27:44Z | 2024-03-22T11:55:05Z | https://github.com/yasm/yasm/issues/218 | 1,648,929,873 | 218 |
[
"yasm",
"yasm"
] | # stack-overflow yasm/modules/parsers/nasm/nasm-parse.c:1235 in parse_expr1
## project address
https://github.com/yasm/yasm
## info
OS：Ubuntu20.04 TLS
Build: ./autogen.sh && make distclean && CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-fra... | stack-overflow yasm/modules/parsers/nasm/nasm-parse.c:1235 in parse_expr1 | https://api.github.com/repos/yasm/yasm/issues/217/comments | 1 | 2023-03-31T08:22:30Z | 2024-03-22T11:56:45Z | https://github.com/yasm/yasm/issues/217 | 1,648,921,272 | 217 |
[
"yasm",
"yasm"
] | # SEGV yasm/modules/preprocs/nasm/nasm-pp.c in delete_Token
## project address
https://github.com/yasm/yasm
## info
OS：Ubuntu20.04 TLS
Build: ./autogen.sh && make distclean && CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" .... | SEGV yasm/modules/preprocs/nasm/nasm-pp.c in delete_Token | https://api.github.com/repos/yasm/yasm/issues/216/comments | 13 | 2023-03-31T08:02:18Z | 2024-03-22T12:02:52Z | https://github.com/yasm/yasm/issues/216 | 1,648,877,295 | 216 |
[
"yasm",
"yasm"
] | # SEGV yasm/libyasm/expr.c:87:44 in yasm_expr_create
## project address
https://github.com/yasm/yasm
## info
OS：Ubuntu20.04 TLS
Build: ./autogen.sh && make distclean && CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" ./config... | SEGV yasm/libyasm/expr.c:87:44 in yasm_expr_create | https://api.github.com/repos/yasm/yasm/issues/215/comments | 1 | 2023-03-31T07:56:32Z | 2024-03-21T12:41:09Z | https://github.com/yasm/yasm/issues/215 | 1,648,868,122 | 215 |
[
"yasm",
"yasm"
] | # stack-buffer-overflow yasm/yasm+0x43b466 in vsprintf
## project address
https://github.com/yasm/yasm
## info
OS：Ubuntu20.04 TLS
Build: ./autogen.sh && make distclean && CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" ./conf... | stack-buffer-overflow yasm/yasm+0x43b466 in vsprintf | https://api.github.com/repos/yasm/yasm/issues/214/comments | 1 | 2023-03-30T13:06:13Z | 2024-03-21T12:42:39Z | https://github.com/yasm/yasm/issues/214 | 1,647,586,741 | 214 |
[
"yasm",
"yasm"
] | An attempted compilation of v1.3.0 via EasyBuild on a machine with the Intel Xeon Platinum 8352Y CPU processor resulted in:
./genmacro win64-nasm.c win64_nasm_stdmac ./modules/objfmts/coff/win64-nasm.mac
./genmacro win64-gas.c win64_gas_stdmac ./modules/objfmts/coff/win64-gas.mac
./genstring license_msg license.c ... | Segfault on Intel Xeon Platinum 8352Y CPU | https://api.github.com/repos/yasm/yasm/issues/213/comments | 0 | 2023-03-29T14:35:48Z | 2023-03-29T14:35:48Z | https://github.com/yasm/yasm/issues/213 | 1,645,951,960 | 213 |
[
"yasm",
"yasm"
] | null | Documentation doesn't explain how to run tests | https://api.github.com/repos/yasm/yasm/issues/212/comments | 0 | 2023-03-12T02:05:55Z | 2023-03-12T02:05:55Z | https://github.com/yasm/yasm/issues/212 | 1,620,206,094 | 212 |
[
"yasm",
"yasm"
] | The last release was in 2014, and there were a lot of commits up until 2022.
| Plans to make a release? | https://api.github.com/repos/yasm/yasm/issues/211/comments | 1 | 2023-03-11T23:57:58Z | 2023-12-12T18:27:10Z | https://github.com/yasm/yasm/issues/211 | 1,620,181,617 | 211 |
[
"yasm",
"yasm"
] |
I found a memory leak bug in yasm.
Please confirm.
Thanks!
### Test Environment
Ubuntu 20.04, 64 bit yasm (version: v1.3.0 ;master)
### How to trigger
Compile the program with AddressSanitizer
Run command
$ touch u
$ ./yasm -ium u
### Details
ASAN report
$./yasm -ium u
```
yasm: file name ... | yasm memory leak | https://api.github.com/repos/yasm/yasm/issues/210/comments | 5 | 2023-03-01T02:27:11Z | 2024-03-22T11:43:38Z | https://github.com/yasm/yasm/issues/210 | 1,604,119,944 | 210 |
[
"yasm",
"yasm"
] |
I found a heap-use-after-free in yasm.
Please confirm.
Thanks!
Test Environment
Ubuntu 20.04, 64 bit yasm (version: v1.3.0 ;master)
How to trigger
Compile the program with AddressSanitizer
Run command $ ./yasm -w -W -M $PoC
Details
ASAN report
$./yasm -w -W -M $PoC
```
yasm: warning: unrecogni... | yasm heap use-after-free bug | https://api.github.com/repos/yasm/yasm/issues/209/comments | 1 | 2023-03-01T02:17:35Z | 2023-05-10T05:20:07Z | https://github.com/yasm/yasm/issues/209 | 1,604,108,494 | 209 |
[
"yasm",
"yasm"
] |
I found a heap-use-after-free in yasm.
Please confirm.
Thanks!
Test Environment
Ubuntu 20.04, 64 bit yasm (version: v1.3.0 ;master)
How to trigger
Compile the program with AddressSanitizer
Run command $ ./yasm -w -W -M $PoC
Details
ASAN report
$./yasm -w -W -M $PoC
```
yasm: warning: unrecogni... | yasm heap use-after-free bug | https://api.github.com/repos/yasm/yasm/issues/208/comments | 1 | 2023-03-01T02:08:44Z | 2023-05-10T05:20:11Z | https://github.com/yasm/yasm/issues/208 | 1,604,101,306 | 208 |
[
"yasm",
"yasm"
] | I found a heap-use-after-free in yasm.
Please confirm.
Thanks!
Test Environment
Ubuntu 20.04, 64 bit yasm (version: v1.3.0 ;master)
How to trigger
Compile the program with AddressSanitizer
Run command $ ./yasm -w -W -M $PoC
Details
ASAN report
$./yasm -w -W -M $PoC
```
yasm: warning: unrecognized ... | yasm heap use-after-free bug | https://api.github.com/repos/yasm/yasm/issues/207/comments | 1 | 2023-03-01T02:03:35Z | 2023-05-10T05:20:08Z | https://github.com/yasm/yasm/issues/207 | 1,604,096,378 | 207 |
[
"yasm",
"yasm"
] | yasm heap buffer overflow
I found a heap-buffer-overflow in yasm.
Please confirm.
Thanks!
Test Environment
Ubuntu 20.04, 64 bit yasm (version: v1.3.0 ;master)
How to trigger
Compile the program with AddressSanitizer
Run command $ ./yasm -s -o abc --force-strict $PoC
Details
ASAN report
$./yasm -s ... | yasm heap buffer overflow | https://api.github.com/repos/yasm/yasm/issues/206/comments | 1 | 2023-03-01T01:50:12Z | 2024-03-22T11:53:56Z | https://github.com/yasm/yasm/issues/206 | 1,604,082,214 | 206 |
[
"yasm",
"yasm"
] | how to fix below error occurring with yasm 1.3 ?
configure: error: Standard (ANSI/ISO C89) header files are required.
Error doesn't occur with yasm 1.2
| autogen.sh error | https://api.github.com/repos/yasm/yasm/issues/205/comments | 0 | 2023-02-07T04:08:51Z | 2023-02-07T04:08:51Z | https://github.com/yasm/yasm/issues/205 | 1,573,650,108 | 205 |
[
"yasm",
"yasm"
] | According to the NASM docs https://www.nasm.us/xdoc/2.15.05/html/nasmdoc3.html#section-3.4.2
> Strings enclosed in backquotes support C-style \–escapes for special characters.
This does not appear to be the case with yasm:
```nasm
; hello.asm
global _start
section .text
_start:
mov rax, 1
mov rdi, 1
m... | Support for backquote strings? | https://api.github.com/repos/yasm/yasm/issues/203/comments | 0 | 2022-12-04T19:53:13Z | 2022-12-04T19:55:53Z | https://github.com/yasm/yasm/issues/203 | 1,475,129,302 | 203 |
[
"yasm",
"yasm"
] | Add `TRASHIT()` macro to set pointer to NULL in `libyasm/compat-queue.h`.
This is just a hardening measure to make sure stale pointers are not left in next/prev struct members.
Also fixed here:
[Bug 247685](https://bugs.webkit.org/show_bug.cgi?id=247685): Add TRASHIT() macro to set pointer to NULL in yasm/liby... | Add TRASHIT() macro to set pointer to NULL in libyasm/compat-queue.h | https://api.github.com/repos/yasm/yasm/issues/202/comments | 0 | 2022-11-12T03:56:28Z | 2022-11-12T03:56:28Z | https://github.com/yasm/yasm/issues/202 | 1,446,227,227 | 202 |
[
"yasm",
"yasm"
] | Trying build [libdav1d](https://code.videolan.org/videolan/dav1d) asm source for arm
Here's command i use "yasm -f elf64 -p gas dav1d/src
and then I catch an error
<img width="543" alt="SegfaultMacos" src="https://user-images.githubusercontent.com/45670849/187673129-56ead6fe-784b-41bb-80c7-cd7089e6ee80.png">
Wher... | segmentation fault on MacOS Monterey 12.2 | https://api.github.com/repos/yasm/yasm/issues/199/comments | 2 | 2022-08-31T11:54:42Z | 2023-07-15T13:54:13Z | https://github.com/yasm/yasm/issues/199 | 1,357,227,323 | 199 |
[
"yasm",
"yasm"
] |
how to fix the error on ubuntu 22.04 ? thanks
checking for sys/stat.h... (cached) yes
configure: error: Standard (ANSI/ISO C89) header files are required.
works on ubuntu 18.04 | autogen.sh error on ubuntu 22.04 | https://api.github.com/repos/yasm/yasm/issues/197/comments | 0 | 2022-07-21T20:07:40Z | 2022-07-21T20:07:40Z | https://github.com/yasm/yasm/issues/197 | 1,313,745,509 | 197 |
[
"yasm",
"yasm"
] | Hi,
When i used -f dosexe option, I found that yasm crashed.
<img width="437" alt="image" src="https://user-images.githubusercontent.com/39018042/172167231-dcb55bf1-3068-4697-ae50-15205868dac0.png">
Here is the command : ```./yasm -f dosexe ./poc```
My poc : https://gist.githubusercontent.com/naihsin/cc5318fd1f06... | Maybe there is a buffer overflow bug in yasm_error_set_va() libyasm/errwarn.c | https://api.github.com/repos/yasm/yasm/issues/196/comments | 0 | 2022-06-06T13:12:09Z | 2022-06-06T13:12:09Z | https://github.com/yasm/yasm/issues/196 | 1,261,829,266 | 196 |
[
"yasm",
"yasm"
] | error description:
when the argument is set to " -o . " (there are other effective conditions to crash when using with VS2022l)
the function "yasm__createpath(objdir_pathname)" returns 0xffffffff which is -1 as index,
objdir_pathname[i] = '/';
objdir_pathname[i + 1] = '\0';
will write the b... | Memory error in vsyasm resulting in crash | https://api.github.com/repos/yasm/yasm/issues/195/comments | 1 | 2022-05-27T04:33:02Z | 2022-06-02T03:57:56Z | https://github.com/yasm/yasm/issues/195 | 1,250,323,068 | 195 |
[
"yasm",
"yasm"
] |
**Description:**
An invalid memory address dereference was discovered at modules/preprocs/nasm/nasm-pp.c:3494. The vulnerability causes a segmentation fault and application crash.
**Version:**
```
./yasm --version
yasm 1.3.0.52.g4176
Compiled on Dec 16 2021.
Copyright (c) 2001-2014 Peter Johnson and ot... | An invalid memory address dereference at modules/preprocs/nasm/nasm-pp.c:3494 | https://api.github.com/repos/yasm/yasm/issues/194/comments | 0 | 2021-12-16T14:48:18Z | 2021-12-16T14:48:18Z | https://github.com/yasm/yasm/issues/194 | 1,082,283,708 | 194 |
[
"yasm",
"yasm"
] | enviroment:win10 vs2019（MSVC140, 141）
| yasm-tool[core] is only supported on 'native & !uwp' | https://api.github.com/repos/yasm/yasm/issues/193/comments | 3 | 2021-11-22T03:25:24Z | 2022-02-11T12:14:29Z | https://github.com/yasm/yasm/issues/193 | 1,059,629,490 | 193 |
[
"yasm",
"yasm"
] | On this page:
https://en.wikipedia.org/wiki/Comparison_of_assemblers#x86-64_assemblers
Yasm is listed as "not in active development". This stopped me considering it until I went to github and saw that development is continuing. But I didn't want to change that status myself in case you're just maintaining? | Wikipedia says Yasm is not in active development | https://api.github.com/repos/yasm/yasm/issues/191/comments | 0 | 2021-11-12T10:10:14Z | 2021-11-12T10:10:14Z | https://github.com/yasm/yasm/issues/191 | 1,051,794,786 | 191 |
[
"yasm",
"yasm"
] | Hi there, I was unable to download a release due to an expired certificate http://www.tortall.net/projects/yasm/releases/yasm-1.3.0.tar.gz
@PeterJohnson | Cert Expired www.tortall.net | https://api.github.com/repos/yasm/yasm/issues/190/comments | 4 | 2021-11-10T12:36:41Z | 2021-11-11T02:28:03Z | https://github.com/yasm/yasm/issues/190 | 1,049,771,004 | 190 |
[
"yasm",
"yasm"
] | It seems that immediate operands using characters are unsupported.
```
$ cat >| fuck.s
.globl main
main:
movb $'\n', %eax
ret
$ as -fatal-warnings -o /dev/null fuck.s
$ yasm -Werror -felf64 -pgas -o /dev/null fuck.s
: error: warnings being treated as errors
fuck.s:3: error: unexpected end of file in str... | Character immediates appear to be unsupported when using the GNU parser? | https://api.github.com/repos/yasm/yasm/issues/188/comments | 1 | 2021-11-01T13:23:34Z | 2021-11-01T13:27:37Z | https://github.com/yasm/yasm/issues/188 | 1,041,170,559 | 188 |
[
"yasm",
"yasm"
] | yasm.s:9: error: expression missing after `$'
yasm.s:22: error: directive `.global' requires an argument
yasm.s:23: error: label or instruction expected at start of line
s to o
.global xxxxf
xxxxf:
pushq %rbp
movq %rsp, %rbp
subq $16, %rsp
.LB1:
#instruction start "1 <- temporary":
#instruction s... | bug? $ | https://api.github.com/repos/yasm/yasm/issues/187/comments | 4 | 2021-10-28T22:30:05Z | 2022-05-26T07:16:25Z | https://github.com/yasm/yasm/issues/187 | 1,039,004,648 | 187 |
[
"yasm",
"yasm"
] | Here is a small example of how I can reliably trigger it:
```c
#include <libyasm/bitvect.h>
#include <stdlib.h>
int main() {
wordptr v = BitVector_Create(64, 1);
BitVector_Destroy(v);
void* p = malloc(1024);
free(p);
return 0;
}
```
Running it gives me:
```
small.o: malloc.c:2539: ... | Heap corruption in BitVector_Create (and other bitvector functions) | https://api.github.com/repos/yasm/yasm/issues/185/comments | 1 | 2021-08-19T12:34:22Z | 2021-08-19T12:43:43Z | https://github.com/yasm/yasm/issues/185 | 974,616,114 | 185 |
[
"yasm",
"yasm"
] | This seems to have occurred again as of 8 days ago: https://github.com/yasm/yasm/issues/106
I was trying to install the ffmpeg:x86-windows package via vcpkg on my Windows machine, which depends on yasm and currently points to https://www.tortall.net/projects/yasm/snapshots/v1.3.0.6.g1962/yasm-1.3.0.6.g1962.exe
ht... | Certificate for https://www.tortall.net has expired, again | https://api.github.com/repos/yasm/yasm/issues/182/comments | 7 | 2021-07-27T19:22:25Z | 2021-08-11T16:22:20Z | https://github.com/yasm/yasm/issues/182 | 954,195,887 | 182 |
[
"yasm",
"yasm"
] | Regarding `UWOP_SET_FPREG`, according to https://docs.microsoft.com/en-us/cpp/build/exception-handling-x64?view=msvc-160:
> The operation info field is reserved and shouldn't be used.
But yasm appears to set it to the frame pointer register: https://github.com/yasm/yasm/blob/41762bead150fdae59687b35c8acd1c4ae0f15... | Win64 unwind data - UWOP_SET_FPREG reserved info field is set | https://api.github.com/repos/yasm/yasm/issues/181/comments | 1 | 2021-07-20T00:50:30Z | 2021-11-01T13:41:41Z | https://github.com/yasm/yasm/issues/181 | 948,142,441 | 181 |
[
"yasm",
"yasm"
] | Using this test file to run the GAS-style preprocessor, yasm crashes:
```
.set counter, 0
.macro REPEATER_2 count=5
.rept \count
.set counter, counter+1
.endr
.endm
REPEATER_2
```
Command line:
```bash
yasm -r gas -e yasm_crash.S -o yasm_crash.i
```
Output:
```
free(): invalid pointer
```
Backt... | GAS: set inside repm crashes | https://api.github.com/repos/yasm/yasm/issues/176/comments | 9 | 2021-05-19T13:44:00Z | 2023-05-13T04:13:45Z | https://github.com/yasm/yasm/issues/176 | 895,464,774 | 176 |
[
"yasm",
"yasm"
] | System info:
Ubuntu 16.04.6 LTS, X64, gcc 5.4.0, yasm (latest master 009450c)
Compile Command:
```
$ ./autogen.sh
make distclean
CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" ./configure --prefix=$PWD/build --disable-shared
ma... | A NULL pointer dereference in the function hash() modules/preprocs/nasm/nasm-pp.c:1114 | https://api.github.com/repos/yasm/yasm/issues/175/comments | 1 | 2021-05-19T08:30:54Z | 2024-03-21T11:46:29Z | https://github.com/yasm/yasm/issues/175 | 895,151,364 | 175 |
[
"yasm",
"yasm"
] | System info:
Ubuntu 16.04.6 LTS, X64, gcc 5.4.0, yasm (latest master 009450c)
Compile Command:
```
$ ./autogen.sh
make distclean
CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" ./configure --prefix=$PWD/build --disable-shared
ma... | A NULL pointer dereference in the function yasm_expr__copy_except() libyasm/expr.c:999 | https://api.github.com/repos/yasm/yasm/issues/174/comments | 2 | 2021-05-19T08:30:07Z | 2024-03-22T14:00:39Z | https://github.com/yasm/yasm/issues/174 | 895,150,639 | 174 |
[
"yasm",
"yasm"
] | System info:
Ubuntu 16.04.6 LTS, X64, gcc 5.4.0, yasm (latest master 009450c)
Compile Command:
```
$ ./autogen.sh
make distclean
CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" ./configure --prefix=$PWD/build --disable-shared
ma... | A NULL pointer dereference in the function expand_mmacro() modules/preprocs/nasm/nasm-pp.c:4764 | https://api.github.com/repos/yasm/yasm/issues/173/comments | 1 | 2021-05-19T08:29:17Z | 2024-03-21T12:35:36Z | https://github.com/yasm/yasm/issues/173 | 895,149,848 | 173 |
[
"yasm",
"yasm"
] | System info:
Ubuntu 16.04.6 LTS, X64, gcc 5.4.0, yasm (latest master 009450c)
I think it is probably a similar issue as [#142](https://github.com/yasm/yasm/issues/142)
Compile Command:
```
$ ./autogen.sh
make distclean
CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanit... | A NULL pointer dereference in the function expand_smacro() modules/preprocs/nasm/nasm-pp.c:4229 | https://api.github.com/repos/yasm/yasm/issues/172/comments | 1 | 2021-05-19T08:28:18Z | 2024-03-21T12:36:44Z | https://github.com/yasm/yasm/issues/172 | 895,148,925 | 172 |
[
"yasm",
"yasm"
] | System info:
Ubuntu 16.04.6 LTS, X64, gcc 5.4.0, yasm (latest master 009450c)
I think it is probably a similar issue as [#151](https://github.com/yasm/yasm/issues/151)
Compile Command:
```
$ ./autogen.sh
make distclean
CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanit... | A NULL pointer dereference in the function expand_mmac_params() modules/preprocs/nasm/nasm-pp.c:3861 | https://api.github.com/repos/yasm/yasm/issues/171/comments | 2 | 2021-05-19T08:27:21Z | 2024-03-21T11:48:05Z | https://github.com/yasm/yasm/issues/171 | 895,147,985 | 171 |
[
"yasm",
"yasm"
] | System info:
Ubuntu 16.04.6 LTS, X64, gcc 5.4.0, yasm (latest master 009450c)
Compile Command:
```
$ ./autogen.sh
make distclean
CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" ./configure --prefix=$PWD/build --disable-shared
ma... | A NULL pointer dereference in the function find_cc() modules/preprocs/nasm/nasm-pp.c:3815 | https://api.github.com/repos/yasm/yasm/issues/170/comments | 1 | 2021-05-19T08:26:28Z | 2024-03-21T12:44:18Z | https://github.com/yasm/yasm/issues/170 | 895,147,145 | 170 |
[
"yasm",
"yasm"
] | System info:
Ubuntu 16.04.6 LTS, X64, gcc 5.4.0, yasm (latest master 009450c)
I think it is probably a similar issue as [#142](https://github.com/yasm/yasm/issues/142)
Compile Command:
```
$ ./autogen.sh
make distclean
CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsaniti... | A NULL pointer dereference in the function do_directive() modules/preprocs/nasm/nasm-pp.c:2355 | https://api.github.com/repos/yasm/yasm/issues/169/comments | 1 | 2021-05-19T08:25:00Z | 2024-03-21T11:40:51Z | https://github.com/yasm/yasm/issues/169 | 895,145,758 | 169 |
[
"yasm",
"yasm"
] | System info:
Ubuntu 16.04.6 LTS, X64, gcc 5.4.0, yasm (latest master 009450c)
Compile Command:
```
$ ./autogen.sh
make distclean
CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" ./configure --prefix=$PWD/build --disable-shared
ma... | A NULL pointer dereference in the function if_condition() modules/preprocs/nasm/nasm-pp.c:2134 | https://api.github.com/repos/yasm/yasm/issues/168/comments | 1 | 2021-05-19T08:24:08Z | 2024-03-21T11:51:21Z | https://github.com/yasm/yasm/issues/168 | 895,144,888 | 168 |
[
"yasm",
"yasm"
] | System info:
Ubuntu 16.04.6 LTS, X64, gcc 5.4.0, yasm (latest master 009450c)
Compile Command:
```
$ ./autogen.sh
make distclean
CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" ./configure --prefix=$PWD/build --disable-shared
ma... | A NULL pointer dereference in the function nasm_parser_directive() modules/parsers/nasm/nasm-parse.c:1596 | https://api.github.com/repos/yasm/yasm/issues/167/comments | 1 | 2021-05-19T08:23:17Z | 2024-03-21T11:50:13Z | https://github.com/yasm/yasm/issues/167 | 895,144,100 | 167 |
[
"yasm",
"yasm"
] | System info:
Ubuntu 16.04.6 LTS, X64, gcc 5.4.0, yasm (latest master 009450c)
I think it is probably a similar issue as [#83](https://github.com/yasm/yasm/issues/83)
Compile Command:
```
$ ./autogen.sh
make distclean
CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsan... | A NULL pointer dereference in the function yasm_expr_get_intnum() libyasm/expr.c:1263 | https://api.github.com/repos/yasm/yasm/issues/166/comments | 4 | 2021-05-19T08:22:19Z | 2024-03-22T14:15:04Z | https://github.com/yasm/yasm/issues/166 | 895,143,168 | 166 |
[
"yasm",
"yasm"
] | System info:
Ubuntu 16.04.6 LTS, X64, gcc 5.4.0, yasm (latest master 009450c)
I think it is probably a similar issue as [#126](https://github.com/yasm/yasm/issues/126
)
Compile Command:
```
$ ./autogen.sh
make distclean
CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsa... | AddressSanitizer: heap-use-after-free in expr_traverse_nodes_post() libyasm/expr.c:1112 | https://api.github.com/repos/yasm/yasm/issues/165/comments | 1 | 2021-05-19T08:21:12Z | 2024-03-21T12:28:49Z | https://github.com/yasm/yasm/issues/165 | 895,142,015 | 165 |
[
"yasm",
"yasm"
] | System info:
Ubuntu 16.04.6 LTS, X64, gcc 5.4.0, yasm (latest master 009450c)
Compile Command:
```
$ ./autogen.sh
make distclean
CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" ./configure --prefix=$PWD/build --disable-shared
ma... | AddressSanitizer: heap-buffer-overflow in inc_fopen() modules/preprocs/nasm/nasm-pp.c:1835 | https://api.github.com/repos/yasm/yasm/issues/164/comments | 4 | 2021-05-19T08:20:09Z | 2022-12-14T17:47:19Z | https://github.com/yasm/yasm/issues/164 | 895,140,978 | 164 |
[
"yasm",
"yasm"
] | System info:
Ubuntu 16.04.6 LTS, X64, gcc 5.4.0, yasm (latest master 009450c)
Compile Command:
```
$ ./autogen.sh
make distclean
CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" ./configure --prefix=$PWD/build --disable-shared
ma... | AddressSanitizer: heap-use-after-free in pp_getline() modules/preprocs/nasm/nasm-pp.c:5024 | https://api.github.com/repos/yasm/yasm/issues/163/comments | 1 | 2021-05-19T08:19:19Z | 2024-03-21T12:37:57Z | https://github.com/yasm/yasm/issues/163 | 895,140,170 | 163 |
[
"yasm",
"yasm"
] | System info:
Ubuntu 16.04.6 LTS, X64, gcc 5.4.0, yasm (latest master 009450c)
Compile Command:
```
$ ./autogen.sh
make distclean
CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" ./configure --prefix=$PWD/build --disable-shared
ma... | AddressSanitizer: heap-use-after-free in error() modules/preprocs/nasm/nasm-pp.c:4830 | https://api.github.com/repos/yasm/yasm/issues/162/comments | 1 | 2021-05-19T08:17:11Z | 2024-03-21T12:39:00Z | https://github.com/yasm/yasm/issues/162 | 895,137,925 | 162 |
[
"yasm",
"yasm"
] | System info:
Ubuntu 16.04.6 LTS, X64, gcc 5.4.0, yasm (latest master 009450c)
I think it is probably a similar issue as [#149](https://github.com/yasm/yasm/issues/149)
Compile Command:
```
$ ./autogen.sh
make distclean
CC=gcc CXX=g++ CFLAGS="-fsanitize=address -fno-omit-frame-pointer -g" CXXFLAGS="-fsanit... | AddressSanitizer: heap-use-after-free in yasm_intnum_destroy() libyasm/intnum.c:415 | https://api.github.com/repos/yasm/yasm/issues/161/comments | 3 | 2021-05-19T08:15:14Z | 2024-03-21T11:56:29Z | https://github.com/yasm/yasm/issues/161 | 895,135,903 | 161 |
[
"yasm",
"yasm"
] | Please tell me how to address the zmm registers?
`helloWorld.asm:17: error: undefined symbol `zmm1' (first use)` | error: undefined symbol `zmm1' | https://api.github.com/repos/yasm/yasm/issues/159/comments | 0 | 2021-02-03T23:06:20Z | 2021-02-03T23:06:20Z | https://github.com/yasm/yasm/issues/159 | 800,772,221 | 159 |
[
"yasm",
"yasm"
] | In current vsyasm.targets this line:
`CommandLineTemplate="$(MSBuildThisFileDirectory)\vsyasm.exe -Xvc -f %(YASM.Platform) [AllOptions] [AdditionalOptions] [Inputs]"`
should be cchanged to:
`CommandLineTemplate=""$(MSBuildThisFileDirectory)\vsyasm.exe" -Xvc -f %(YASM.Platform) [AllOptions] [AdditionalOpt... | vyasm fails in folders with spaces in it | https://api.github.com/repos/yasm/yasm/issues/158/comments | 8 | 2020-12-27T15:05:23Z | 2020-12-28T19:34:12Z | https://github.com/yasm/yasm/issues/158 | 775,053,819 | 158 |
[
"yasm",
"yasm"
] | Hi there. when running make check, I got 2/44 tests failed:
1. FAIL: modules/objfmts/elf/tests/amd64/elf_amd64_test.sh
=======================================================
Test elf_amd64_test: O... +3-1/4 75%
** O: elf-rip did not match object file!
2. FAIL: modules/objfmts/elf/tests/gas64/elf_gas64_test... | make check has 2 failed tests (linux amd64) | https://api.github.com/repos/yasm/yasm/issues/157/comments | 3 | 2020-11-10T14:28:27Z | 2021-05-24T23:13:18Z | https://github.com/yasm/yasm/issues/157 | 739,957,551 | 157 |
[
"yasm",
"yasm"
] | `endbr64` is a new psuedo-instruction (well, it's a real instruction on some CPUs that is) used for control flow information using what was previously a multibyte nop encoding:
`\xf3\x0f\x1e\xfa` | No support for endbr64 instruction | https://api.github.com/repos/yasm/yasm/issues/156/comments | 1 | 2020-08-24T19:43:05Z | 2021-11-01T13:08:48Z | https://github.com/yasm/yasm/issues/156 | 684,918,851 | 156 |
[
"yasm",
"yasm"
] | I built yasm with cmake on zsh and installed to a directory "/usr/local/git".
And I could find "/usr/local/git/bin/yasm" and "/usr/local/git/lib/libyasm.dylib".
I set the library path as "export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib:/usr/local/git/lib" in zshrc.
But yasm command cannot find libyasm.dyli... | "dyld: Library not loaded: libyasm.dylib" on macOS 10.15 | https://api.github.com/repos/yasm/yasm/issues/155/comments | 3 | 2020-08-06T16:08:10Z | 2020-08-07T04:10:37Z | https://github.com/yasm/yasm/issues/155 | 674,429,183 | 155 |
[
"yasm",
"yasm"
] | see my PR https://github.com/yasm/yasm/pull/148 | add .note.gnu.property note section support | https://api.github.com/repos/yasm/yasm/issues/154/comments | 0 | 2020-07-16T16:55:24Z | 2020-07-16T16:56:56Z | https://github.com/yasm/yasm/issues/154 | 658,376,702 | 154 |
[
"yasm",
"yasm"
] | Hi guys,
Recently, I want to update yasm in vcpkg ([#12324](https://github.com/microsoft/vcpkg/pull/12324)) to solve some issues, but I got the error message on the pipeline machine:
```
D:\installed\x64-windows\share\vs-yasm\yasm.targets(50,5): error MSB3721: The command ""D:/downloads/tools/yasm/1.3.0.6/x64/"yasm... | yasm exits abnormally on Windows | https://api.github.com/repos/yasm/yasm/issues/153/comments | 4 | 2020-07-09T02:41:04Z | 2020-10-09T08:18:33Z | https://github.com/yasm/yasm/issues/153 | 653,717,823 | 153 |
[
"yasm",
"yasm"
] | # Version
yasm-c9db6d7
# Command
./yasm $FILE -o /tmp/foo
# Bug Type
stack overflow
# Crash file
https://github.com/natalie13m/crashes/blob/master/yasm-c9db6d7/id:000086%2Csig:11%2Csrc:015136%2B014346%2Cop:splice%2Crep:16
# Address Sanitizer output
```
AddressSanitizer:DEADLYSIGNAL
========================... | Stack overflow in parse_expr6(5,4,3,2,1) modules/parsers/nasm/nasm-parse.c | https://api.github.com/repos/yasm/yasm/issues/152/comments | 1 | 2020-06-13T04:46:15Z | 2021-11-01T11:54:03Z | https://github.com/yasm/yasm/issues/152 | 638,095,591 | 152 |
[
"yasm",
"yasm"
] | # Version
yasm-c9db6d7
# Command
./yasm $FILE -o /tmp/foo
# Bug Type
read memory access violation on the zero page
# Crash file
https://github.com/natalie13m/crashes/blob/master/yasm-c9db6d7/id:000104%2Csig:11%2Csrc:005124%2B007559%2Cop:splice%2Crep:64
# Address Sanitizer output
AddressSanitizer:DEADLYSIGNAL... | Access violation near NULL on source operand in expand_mmac_params modules/preprocs/nasm/nasm-pp.c:3861 | https://api.github.com/repos/yasm/yasm/issues/151/comments | 0 | 2020-06-13T04:42:53Z | 2020-06-13T04:42:53Z | https://github.com/yasm/yasm/issues/151 | 638,095,211 | 151 |
[
"yasm",
"yasm"
] | # Version
yasm-c9db6d7
# Command
./yasm $FILE -o /tmp/foo
# Bug Type
read memory access violation on zero page
# Crash file
https://github.com/natalie13m/crashes/blob/master/yasm-c9db6d7/id:000101%2Csig:11%2Csrc:015858%2Cop:havoc%2Crep:64
# Address Sanitizer output
```
AddressSanitizer:DEADLYSIGNAL
=======... | Access violation near NULL on source operand in BitVector_Block_Store libyasm/bitvect.c:3261 | https://api.github.com/repos/yasm/yasm/issues/150/comments | 1 | 2020-06-13T04:35:42Z | 2021-11-01T11:55:53Z | https://github.com/yasm/yasm/issues/150 | 638,094,456 | 150 |
[
"yasm",
"yasm"
] | # Version
yasm-c9db6d7
# Command
./yasm $FILE -o /tmp/foo
# Bug Type:
heap-use-after-free
# Crash file
https://github.com/natalie13m/crashes/blob/master/yasm-c9db6d7/id:000053%2Csig:11%2Csrc:014975%2Cop:havoc%2Crep:4
#Address Sanitizer Output
```
=============================================================... | heap-use-after-free in yasm_intnum_destroy libyasm/intnum.c:415 | https://api.github.com/repos/yasm/yasm/issues/149/comments | 1 | 2020-06-13T04:32:19Z | 2021-11-01T11:55:15Z | https://github.com/yasm/yasm/issues/149 | 638,094,099 | 149 |
[
"yasm",
"yasm"
] | As Python 2 reached EOL, support for Python 3 will be great.
| support Python 3 | https://api.github.com/repos/yasm/yasm/issues/143/comments | 1 | 2020-02-10T09:34:15Z | 2020-02-10T10:00:49Z | https://github.com/yasm/yasm/issues/143 | 562,433,867 | 143 |
[
"yasm",
"yasm"
] | While using yasm 1.3 some errors happen. Poc files can be found [here](https://tortall.lighthouseapp.com/projects/78676/tickets/380-null-ponter-dereference-happends-in-expand_mmac_params-nasmnasm-ppc#ticket-380-3)
### Error One
yasm-1.3 has a null pointer dereference or heap buffer over-read in expand_mmac_params... | yasm-1.3 has some errors leading to Segmentation fault | https://api.github.com/repos/yasm/yasm/issues/142/comments | 0 | 2019-12-20T03:14:52Z | 2019-12-20T03:14:52Z | https://github.com/yasm/yasm/issues/142 | 540,723,091 | 142 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.