Zheng Yu
Zheng Yu
> That must be an old example, since it uses a method that was replaced about 9 months ago (`ql.os.function_arg`). Try updating your Qiling copy and re-running the the following...
我再看了一下，代码在linux是可以跑通的，window下无法正常运行因为缺少一些常量
The multitasking extension is currently only for the MCU, we will improve it in the future
你好，外设的波特率由固件代码本身设置，由于qiling并不模拟外接的外设，所以波特率并无实际效果。 Sent from my iPhone On May 31, 2023, at 14:16, vgegok ***@***.***> wrote: 如果串口通信的波特率是通过被模拟固件中串口端口的波特率确定的，那我能不能设置一个确定的波特率和固件交互。 如果固件中不定义波特率，而是对上位机发送的数据进行自适应波特率处理，类似STM32的ISP编程，上位机发送0x7F，单片机会通过接收0x7F计算波特率，这种情况就不能进行通信，因为上位机（qiling串口交互）和固件都不能确定波特率。 我能不能设置一个确定的波特率和固件交互。 — Reply to this email directly, view it on GitHub, or unsubscribe....
You are right, it is a deprecated api
Assigned [CVE-2023-43338](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-43338)
I do not have testcases
I believe we may have found a new bug. I made the following change to the code: ```c template AI_FORCE_INLINE bool SkipSpaces(const char_t *in, const char_t **out, const char_t *end)...
Thank you for your suggestion! After revisiting the vulnerability, I found that the issue occurs in the `MarkSlotAllocated` function located in `source/m3_compile.c`: ```c static inline void MarkSlotAllocated (IM3Compilation o, u16...
> I don’t quite understand how this overflow would cause the environment to become `NULL`, but it's certainly a potential overflow. Actually, the process is quite long and complex, involving...