-
**Describe the bug**
The typedesc_test run does not pass a valgrind run, as data is used before it is initialized.
This causes underfined behaviour.
**OpenImageIO version and dependencies**
…
stolk updated
1 month ago
-
### Is your feature request related to a problem ?
Hello! This isn't so much a feature request as a submission of an idea with proof of concept code.
The zpool bar doesn't show the actual capaci…
-
### Description / Steps to reproduce the issue
` gcc -Wall -c bug.c -std=c99`
```c
#include
#define ATTRIBUTE_PRINTF(m, n) __attribute__ ((__format__ (__printf__, m, n)))
#define ATTRIBUTE_P…
-
The debug output in function handle\_saHpiDomainInfoActiveEntries\(\) \(saHpiDomainInfoTable.c, line 353\) uses %d format for an u\_long argument while it should be using %ld.
Reported by: sharkcz
O…
-
This is something that I am unfamiliar with. When I was experimenting a format specification checker for the `printf` family, everything worked as expected until it came to the c16/c64/c128 targets - …
-
The debug output in function handle_saHpiDomainInfoActiveEntries() (saHpiDomainInfoTable.c, line 353) uses %d format for an u_long argument while it should be using %ld.
Reported by: horakdan
-
E.g. given:
```
#include
int
main()
{
printf("num1=%d, num2=%u\n", 3, 4);
return 0;
}
```
The **.go** file excerpt reads:
```
func main() {
noarch.Printf((&[]byte("num1=%d, …
-
## Context
I'm trying to do Windows SEH in Odin, when exception occurred, catch it and write a dump file for later debugging.
* Operating System & Odin Version:
* Please paste `odin report` out…
ccll updated
17 minutes ago
-
# What is "VarArgs?"
Java supports "variable arity" methods (also called varargs). These allow one to write a function like
```java
public void printf(String format, Object... args) {
// ...…
-
There are APIs throughout the codebase that accept printf-style-formats. Now that our internal `printf` implementation has been removed, https://github.com/dotnet/runtime/pull/81243, these APIs should…