tr4v3ler

Results 17 comments of tr4v3ler

Someone once implemented the capture of the link command on an old bear version. The link is as follows: [bear](https://github.com/Machiry/Bear) Hope to provide some reference.

The following output is a case: ``` "arguments": [ "-EL", "-r" ], "directory": "/home/tr4v3ler/data/tools/difuze/mtk_kernel_0/kernel-3.18/out", "files": [ "drivers/misc/mediatek/video/common/mtkfb_fence.o", "drivers/misc/mediatek/video/common/fbconfig_kdebug.o", "drivers/misc/mediatek/video/common/aal20/built-in.o", "drivers/misc/mediatek/video/common/corr10/built-in.o", "drivers/misc/mediatek/video/common/color20/built-in.o" ], "loader": "ld", "output": [ "-o", "drivers/misc/mediatek/video/common/built-in.o" ] ```...

> Hey @tr4v3ler , thanks for the report. My first guess is that you are passing this to the C compiler and not to the CXX compiler. Then I tried...

> > Hey @tr4v3ler , thanks for the report. My first guess is that you are passing this to the C compiler and not to the CXX compiler. > >...

> Thanks, to coming back... could you run the build in verbose mode? (set the environment variable `VERBOSE=1` before running `make`) That case you can observe the compiler invocation. >...

> [d5b8dae](https://github.com/Neutree/COMTool/commit/d5b8daef8fe2f583abc80064a42bc52276162d8d) 改好了,现在输入框空了会变成默认的 300ms(接收200ms),不会弹框警告了,软件闪退可能是旧版的问题,现在不存在了 请问收发窗口的定时发送功能所需发送的信息应该在哪里编辑?右下角的输入框里面编辑没有生效,是要打开侧边栏在自定义发送那里编辑吗?

> @tr4v3ler ![image](https://user-images.githubusercontent.com/8625829/219658227-099ce2ad-f724-43bf-8c4b-53ed30010d75.png) > > 勾上左边的定时发送,下面的正常发送框输入内容,然后点击发送就会自动发了 收到,多谢!

I have encountered a similar problem: ``` failed to create instance: failed to run ["adb" "-s" "XXXX" "shell" "find /data/syzkaller* -type l -exec unlink {} \\; && rm -Rf /data/syzkaller*"]:...

These problems occur frequently, are there currently any ways to avoid them? ``` 2023/08/24 15:11:03 failed to create instance: failed to run ["adb" "-s" "XXXX" "shell" "find /data/syzkaller* -type l...

> Could you please check if #4171 changes anything? Though the chances that it's indeed the fix are near zero.. > > I unfortunately don't have any devices nearby to...