two issues with new register calling convention
@D0ntPanic ya está trabajando en esto.
Desde el 21/9/2026.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 64/100
- Tipo de issue
- Error
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- cpp
- Área
- compilers, reverse-engineering
Línea de trabajo
Start in arch/x86/arch_x86.cpp at the x86 register calling-convention implementation, especially IsStackAdjustedOnReturn and GetCallLayout, and compare the proposed layout with GetDefaultCallLayout. Verify callee cleanup and that an indirect result pointer occupies the slot after declared parameters: EAX with none, EDX after one, and the stack after EAX, EDX, and ECX are used.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
The x86 register calling convention added in the recent CC refactor needs two core fixes to be laid out
correctly: callee stack cleanup, and the hidden pointer for an indirectly returned result going in the argument slot following the declared parameters (EAX with no parameters, EDX after one, the stack once EAX/EDX/ECX
are taken). Without them, every Delphi prototype with a stack argument or a string/record/variant result has its arguments shifted.
Found this while working on a delphi plugin, it certainly produces better results but haven't validated it fully by hand:
diff --git a/arch/x86/arch_x86.cpp b/arch/x86/arch_x86.cpp
index 35d58a008..966f53c23 100644
--- a/arch/x86/arch_x86.cpp
+++ b/arch/x86/arch_x86.cpp
@@ -4913,11 +4913,56 @@ public:
return type && !type->IsFloat() && type->GetWidth() > 4;
}
+ bool IsStackAdjustedOnReturn() override
+ {
+ return true;
+ }
+
bool AreStackArgumentsPushedLeftToRight() override
{
return true;
}
+ /*! Delphi passes the hidden pointer for an indirectly returned result in the argument slot
+ *following* the declared parameters: EAX for a parameterless function, EDX after one
+ parameter, and the stack once EAX, EDX and ECX are taken. GetIndirectReturnValueLocation
+ cannot express that, because the slot depends on how many parameters precede it, so the
+ whole layout is computed here instead.
+ */
+ CallLayout GetCallLayout(BinaryView* view, const ReturnValue& returnValue, const vector<FunctionParameter>& params,
+ const std::optional<set<uint32_t>>& permittedRegs) override
+ {
+ CallLayout result = GetDefaultCallLayout(view, returnValue, params, permittedRegs);
+ if (!result.returnValue.has_value() || !result.returnValue->indirect)
+ return result;
+
+ // A caller that has pinned the return value to an explicit location keeps it.
+ // MarkNonDefaultParameterLocations clears defaultLocation and re-runs this until the
+ // layout agrees with the location it recorded, so moving a pinned location never
+ // terminates.
+ if (!returnValue.defaultLocation)
+ return result;
+
+ // Lay the call out a second time with the hidden pointer appended as an ordinary trailing
+ // parameter and nothing returned, then split that parameter back off as the return value.
+ vector<FunctionParameter> extended = params;
+ extended.push_back(FunctionParameter("", Type::PointerType(GetArchitecture(), Type::VoidType())));
+ CallLayout appended = GetDefaultCallLayout(view, ReturnValue(Type::VoidType()), extended, permittedRegs);
+ if (appended.parameters.size() != extended.size())
+ return result;
+
+ ValueLocation hidden = appended.parameters.back();
+ hidden.indirect = true;
+ hidden.returnedPointer = result.returnValue->returnedPointer;
+ appended.parameters.pop_back();
+
+ result.parameters = appended.parameters;
+ result.returnValue = hidden;
+ result.stackAdjustment = appended.stackAdjustment;
+ result.registerStackAdjustments = appended.registerStackAdjustments;
+ return result;
+ }
+
- Lenguaje dominante
- C++
- Estrellas
- 1.3k
- Forks
- 298
- Merge medio
- 4 d 13 h
- PR fusionados (30 d)
- 20
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de Vector35/binaryninja-api
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 88/100
Vector35/binaryninja-api#8540 ·
-
normalize time logs from WARP Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
Vector35/binaryninja-api#8446 ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
Vector35/binaryninja-api#8444 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Vector35/binaryninja-api#8441 · 3 comentarios ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Vector35/binaryninja-api#8404 ·
Todos los issues de Vector35/binaryninja-api
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
google/libultrahdr#485 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
godotengine/godot#123776 ·
-
bug
Dificultad 1/5 Menos de una hora Aptitud para principiantes 60/100
-
good first issue
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
-
good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
ros2/common_interfaces#344 ·