Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Windows compatibility (.exe ARM tools)

See original GitHub issue

I managed to build and install puncover on my Windows 10 machine. When I try to run it, I get the following error :

parsing ELF at firmware.elf Traceback (most recent call last): File "C:\Python\Python37-32\Scripts\puncover-script.py", line 11, in <module> load_entry_point('puncover==0.0.1', 'console_scripts', 'puncover')() File "C:\Python\Python37-32\lib\site-packages\puncover-0.0.1-py3.7.egg\puncover\puncover.py", line 58, in main builder.build_if_needed() File "C:\Python\Python37-32\lib\site-packages\puncover-0.0.1-py3.7.egg\puncover\builders.py", line 32, in build_if_needed self.build() File "C:\Python\Python37-32\lib\site-packages\puncover-0.0.1-py3.7.egg\puncover\builders.py", line 22, in build self.collector.parse_elf(self.get_elf_path()) File "C:\Python\Python37-32\lib\site-packages\puncover-0.0.1-py3.7.egg\puncover\collector.py", line 306, in parse_elf self.parse_assembly_text("".join(self.gcc_tools.get_assembly_lines(elf_file))) File "C:\Python\Python37-32\lib\site-packages\puncover-0.0.1-py3.7.egg\puncover\gcc_tools.py", line 27, in get_assembly_lines return self.gcc_tool_lines('objdump', ['-dslw', os.path.basename(elf_file)], os.path.dirname(elf_file)) File "C:\Python\Python37-32\lib\site-packages\puncover-0.0.1-py3.7.egg\puncover\gcc_tools.py", line 23, in gcc_tool_lines proc = subprocess.Popen([self.gcc_tool_path(name)] + args, stdout=subprocess.PIPE, cwd=cwd) File "C:\Python\Python37-32\lib\site-packages\puncover-0.0.1-py3.7.egg\puncover\gcc_tools.py", line 18, in gcc_tool_path raise Exception("Could not find %s" % path) Exception: Could not find C:\Program Files\...\gcc\arm-none-eabi\bin\objdump

As this is Windows, the objdump tool do exist but as a ‘objdump.exe’ file, not as ‘objdump’.

Would it be possible to check for .exe file and use them for Windows users ?

Issue Analytics

State:
Created 3 years ago
Comments:8 (1 by maintainers)

Top GitHub Comments

5reactions

ckak07commented, Jun 17, 2020

Hello,

before I saw this post i fixed the problem in my own way. You can see the results of my changes in the attached patch-file. If you have any questions about my changes then feel free to concat me.

fixWindowsPaths.patch.txt

0reactions

vChavezBcommented, Dec 11, 2022

Just an FYI. I fixed the OS path dependency issue. Feel free to test my changes

https://github.com/HBehrens/puncover/pull/64

Top Results From Across the Web

Program Compatibility Troubleshooter on Arm

You start the Program Compatibility Troubleshooter manually in the same way on any Windows PC: right-click an executable (.exe) file and ...

Windows Compatibility: ARM, C166, C251, and C51 Tools

The MDK-ARM tools are compatible with: Windows Vista (32-bit or 64-bit) - released January 2007. Windows 7 (32-bit or 64-bit) - released October...

Windows on Arm: This is how well 64-bit emulation is working

Tools to go 64-bit ... Microsoft may have been hoping that many more developers would recompile applications as native Arm versions, because the ......

Best native apps for Windows on Arm: Edge, Zoom, VLC, ...

The popular file archiving tool 7-Zip has been testing a native Arm version for a while, and it's already available as a stable...

Windows 10 on Arm: What you need to know before ...

In addition to UWP apps, Windows 10 on ARM can also run your x86 Win32 apps (such as Adobe Reader) unmodified, with good...