iceman's latest firmware crashes using both mingw and Gator.

phiber · 2017-05-31 08:20:58

As topic, tried running both the mingw compiled .exe with latest git pull and windows exe compiled by Gator.

Crashes whenever i try to do a LF SE:

Unhandled exception at 0x0042355c in proxmark3.exe: 0xC0000005: Access violation reading location 0xffffffff.

This is on Windows 10, seems to have happened due to some update win10 issued maybe?
This is debug window using VS2010

LOG from Gator's window EXE:

Proxmark3 RFID instrument
bootrom: iceman/master/v1.1.0-2035-g9f3d7bb 2017-05-30 15:36:05
os: iceman/master/v1.1.0-2035-g9f3d7bb 2017-05-30 15:36:27
LF FPGA image built for 2s30vq100 on 2015/03/06 at 07:38:04
HF FPGA image built for 2s30vq100 on 2015/11/ 2 at 9: 8: 8

uC: AT91SAM7S256 Rev B
Embedded Processor: ARM7TDMI
Nonvolatile Program Memory Size: 256K bytes. Used: 216650 bytes (83%). Free: 45494 bytes (17%).
Second Nonvolatile Program Memory Size: None
Internal SRAM Size: 64K bytes
Architecture Identifier: AT91SAM7Sxx Series
Nonvolatile Program Memory Type: Embedded Flash Memory
Reading 30000 bytes from device memory

Data fetched
Samples @ 8 bits/smpl, decimation 1:1

Last edited by phiber (2017-05-31 08:23:51)

phiber · 2017-05-31 08:27:42

it seems that it only crashes when i do LF reads:

LF search - crash
lf viking read - crash
lf viking clone 01020304 - OK
hf se - OK

phiber · 2017-05-31 09:24:55

i recompiled and flashback iceman's version 1.6.9 and all is well.. must be something in the new code that is doing this..

ntk · 2017-05-31 12:16:31

Sorry my mistake. I like to see the window OS/linux term err msg not the pm3 log.

Could you see the new graph tool when using latest iceman fork, mine is from 27/04

in later SW call "LF SE" turned to "lf sea" to work, the old boys seem to prepare secret battle plan in the background

edit:
i just build iceman fork today in gator upgraded proxspace environment and test it. I apology for my mistakes I post earlier:
- in iceman fork "lf se" still accepted
- iceman fork still uses the old graphic tool.
- I see the crash too. in pure iceman fork the new dll files in client directory need to be archive too, or PM3 crashed.
My system is window7

Last edited by ntk (2017-05-31 22:02:00)

gator96100 · 2017-06-01 01:01:11

Could be related to the proxmark3 "easy", but I'm not familiar with the proxmark3 "easy" limitations.

@ntk You managed to fix this issue? What dlls are missing?

Last edited by gator96100 (2017-06-01 01:01:56)

ntk · 2017-06-01 03:32:18

I suspect the new graphic tool and somehow iceman has recently started to touch some of Marshmellow's code. so theoretically, because iceman will need to use the new graphic tool at some point, we can bring over all the dll files which are needed in the MM42 or main repo.

But if we don't like the blind trial method, too heavy artillery, then copy the file qwindows.dll over into (iceman sw)/client/plattforms/ would resolve the crash.

This solution is only for iceman's fork release from May 2017
My is win7 I am not sure the fix work on other OS, but pls state your result, would help others's orientation.

Last edited by ntk (2017-06-01 10:21:06)

gator96100 · 2017-06-01 11:45:10

@ntk the qwindows.dll is already included in the precompiled builds, so this is not the solution to the issue. If you run the proxmark3.exe directly from the cloned git repository you will need to copy all dependencies. If you run the proxmark3.exe from the mingw terminal you should be fine.

@phiber does hw tune cause a crash? If so it might be related to the graphic tool as ntk suggested.

ntk · 2017-06-01 13:13:58

gator96100 wrote:

@ntk the qwindows.dll is already included in the precompiled builds, so this is not the solution to the issue. If you run the proxmark3.exe directly from the cloned git repository you will need to copy all dependencies. If you run the proxmark3.exe from the mingw terminal you should be fine.
@phiber does hw tune cause a crash? If so it might be related to the graphic tool as ntk suggested.

situation maybe different with precompiled builds, I haven't run those, so I am not sure. do they still crash?

Will look into it this evening. I rebuilt main repo, MM42, iceman all three run stable, not pure git clone (but on my PC there are SW from git + the extra dll files) Only the graphic tool crashes on weak fob, non-fob, non-antenna (non-sense but I chose extreme to test stability)

Are you sure qwindows.dll is already included in iceman's latest SW? If you download the zip file or you can run "git clone iceman fork" to a clean directory, and you see the pm3/client/platforms contains no dll file which is needed for this PM3 May 2017 to run stably.

I can demonstrate the crash in once second to next just by removing/renaming only that dll (pls make sure you run exactly the pm3 build from the questionable directory, easy to forget running the right build in the heat of the fight against bugs and I am sure many versions currently prevail on your laptop by the measure of your works)

Last edited by ntk (2017-06-01 13:29:34)

iceman · 2017-06-01 14:01:43

icemanfork needs those qt*.dll files to be downloaded and copied into client/platforms folder.

They are too big files (and not opensourced) to be added to GitHub repo.

phiber · 2017-06-01 15:35:59

gator96100 wrote:

@ntk the qwindows.dll is already included in the precompiled builds, so this is not the solution to the issue. If you run the proxmark3.exe directly from the cloned git repository you will need to copy all dependencies. If you run the proxmark3.exe from the mingw terminal you should be fine.
@phiber does hw tune cause a crash? If so it might be related to the graphic tool as ntk suggested.

Let me try and report back..

the latest iceman crashes for me both the precompiled windows.exe and from the mingw terminal.

gator96100 · 2017-06-03 00:46:42

@phiber just to be clear: No crash on startup? No crash on hf se? Crash on hw tune(with hf antenna only, as well as both)? Crash on lf se? What cpu do you have? Do you have QT installed on your system? I have created 2 iceman builds for you to test.
https://drive.google.com/open?id=0B03wI … kRrbUJVZE0
https://drive.google.com/open?id=0B03wI … lBZTVdibXc

Last edited by gator96100 (2017-06-03 00:57:48)

phiber · 2017-06-03 11:30:42

I am running a Surface Pro 3, i5 8gb ram, on windows 10, latest updates.
Using a proxmark3 Eazy from China.

I have the full libraries for windows installed following the instructions on https://github.com/iceman1001/proxmark3
Was able to compile and run find until recently.

Here's with the latest pull from github:

$ proxmark3 com3
Proxmark3 RFID instrument
bootrom: iceman/master/v1.1.0-2035-g9f3d7bb-dirty-unclean 2017-05-31 15:41:34
os: iceman/master/v1.1.0-2035-g9f3d7bb-dirty-unclean 2017-05-31 15:41:46
LF FPGA image built for 2s30vq100 on 2015/03/06 at 07:38:04
HF FPGA image built for 2s30vq100 on 2015/11/ 2 at 9: 8: 8

uC: AT91SAM7S256 Rev B
Embedded Processor: ARM7TDMI
Nonvolatile Program Memory Size: 256K bytes. Used: 216650 bytes (83%). Free: 45494 bytes (17%).
Second Nonvolatile Program Memory Size: None
Internal SRAM Size: 64K bytes
Architecture Identifier: AT91SAM7Sxx Series
Nonvolatile Program Memory Type: Embedded Flash Memory
pm3 -->

-----------------------------------------------------------------

from MINGW:
hf search - ok
lf search - searches, then crashes when trying to show result

pm3 --> hw tune

Measuring antenna characteristics, please wait......
# LF antenna: 10.04 V @ 125.00 kHz
# LF antenna: 12.65 V @ 134.00 kHz
# LF optimal: 19.25 V @ 144.58 kHz
# HF antenna: 16.62 V @ 13.56 MHz

Crashes at this point when trying to draw the graph.

----

Same behavior with the official Gator EXE.

-----------------------------------------

Now with iceman-test: All commands work! great!
With Iceman-easy: All commands work great!

So what's the difference?

iceman · 2017-06-03 12:49:04

I'd guess the client/platforms folder...

hm.. maybe the instructions should add that part aswell..

gator96100 · 2017-06-03 17:43:45

@phiber I have created some more builds for you to test in order to isolate the problem.
https://drive.google.com/open?id=0B03wI … HU0aVF3SDg
https://drive.google.com/open?id=0B03wI … XFFSWJ5dTQ
https://drive.google.com/open?id=0B03wI … 0RFZWEyX1E
https://drive.google.com/open?id=0B03wI … FE0YlNzaFk
https://drive.google.com/open?id=0B03wI … W9DS2pnWE0
https://drive.google.com/open?id=0B03wI … lRUUXJ1X28

@iceman there should be no need to copy the qt dlls into the client/platforms folder, because the ProxSpace environment sets the QT_QPA_PLATFORM_PLUGIN_PATH variable to the correct folder. The qt dlls need to be copied only when the proxmark3.exe is run outside the mingw terminal.

Last edited by gator96100 (2017-06-03 17:44:07)

iceman · 2017-06-03 17:46:40

in your env yes, but not if you follow the instructions on github/iceman/proxmark3...

where do you set that env var? I'll need to add it to my setup

gator96100 · 2017-06-03 17:52:27

The variable is set in msys/etc/profile. Have a look: https://github.com/Gator96100/ProxSpace … 3aa756fd9b

Threshold · 2017-06-18 08:57:34

gator96100 wrote:

@phiber just to be clear: No crash on startup? No crash on hf se? Crash on hw tune(with hf antenna only, as well as both)? Crash on lf se? What cpu do you have? Do you have QT installed on your system? I have created 2 iceman builds for you to test.
https://drive.google.com/open?id=0B03wI … kRrbUJVZE0
https://drive.google.com/open?id=0B03wI … lBZTVdibXc

Well , I face the same problem while using iceman builds. It will crash when i do "hw tune".
It seems crash when it popup diagram window.
My laptop is Win10 x64.
Do "hw tune" command is ok when i flash official or iceman-easy or iceman-test builds.
And i tested "iceman-add-qt-compile" "iceman-add" "iceman-qt-compile" "iceman-qt-compile-all" "iceman-add-qt-compile-all" these builds,It will crash when i command "hw tune".
Any reply will be appreciate. Thanks for your effort!

Here is my proxmark3 device infomation:

Proxmark3 RFID instrument
bootrom: iceman/master/v1.1.0-2051-ge82496ca 2017-06-17 15:11:42
os: iceman/master/v1.1.0-2051-ge82496ca 2017-06-17 15:11:47
LF FPGA image built for 2s30vq100 on 2015/03/06 at 07:38:04
HF FPGA image built for 2s30vq100 on 2015/11/ 2 at 9: 8: 8

uC: AT91SAM7S256 Rev A
Embedded Processor: ARM7TDMI
Nonvolatile Program Memory Size: 256K bytes. Used: 216650 bytes (83%). Free: 45494 bytes (17%).
Second Nonvolatile Program Memory Size: None
Internal SRAM Size: 256K bytes
Architecture Identifier: AT91SAM7Sxx Series
Nonvolatile Program Memory Type: Embedded Flash Memory

gator96100 · 2017-06-18 13:05:02

@Threshold Does "iceman-no-march" crash too? What CPU do you have? Did you flash the bootloader as well? Did you try to download the ProxSpace environment and compile it yourself?

ntk · 2017-06-18 13:05:38

please specify how it crashed? you have screenshot of crash message, log file ? Did you run the client, connect PM3 then open a data plot, then run hw tu? or run straightly "hw tu"? could you run any other commands (obviously not again the same hw tu :-} becase it aherm ... crashes!), after the crash msg had appeared, or do you have to disconnect PM3 and restart the client cleanly at all

You have any JIT bugger? pls connect it.

PS: Also now-a-days when you say you are window10 64bit, pls which one? the one with or without all the spywares .... sorry to have put salt in to your wounds, but we need to be exact...

Last edited by ntk (2017-06-18 13:16:30)

Threshold · 2017-06-18 14:06:24

gator96100 wrote:

@Threshold Does "iceman-no-march" crash too? What CPU do you have? Did you flash the bootloader as well? Did you try to download the ProxSpace environment and compile it yourself?

1. Yes, the ""iceman-no-march" crash too.
2. My laptop cpu is i5-5200U, Win 10 x64 Professional. When i command "hw tune",after it measure voltage and prepare show diagram,the "proxmark3.exe" just crashed, no extra message,Windows just give me two option: one is close application and the other is debug it. No useful information on "proxmark3.log".
3. As you can see information about my proxmark3, I already flashed the iceman latest bootloader.
4. I haven't download ProxSpace and compile by myself.
Just curious, what difference between "iceman-easy" and normal iceman builds? The "iceman-easy" and "iceman-test" works well in my environment, and the official builds too.

gator96100 · 2017-06-18 15:10:57

"iceman-test" and "iceman-easy" have no compiler optimizations for a specific CPU instruction set and have additional qt dlls included during compiling as well as in the platforms folder. All other test builds should check what of these changes causes the problem.
Here are some other builds to test.
https://drive.google.com/file/d/0B03wIb … Xp4Mk5feGM
https://drive.google.com/open?id=0B03wI … VdPUlQ1Zlk

Last edited by gator96100 (2017-06-18 15:16:46)

Threshold · 2017-06-19 02:08:22

gator96100 wrote:

"iceman-test" and "iceman-easy" have no compiler optimizations for a specific CPU instruction set and have additional qt dlls included during compiling as well as in the platforms folder. All other test builds should check what of these changes causes the problem.
Here are some other builds to test.
https://drive.google.com/file/d/0B03wIb … Xp4Mk5feGM
https://drive.google.com/open?id=0B03wI … VdPUlQ1Zlk

Both of "iceman-add-no-march" / "iceman-add-qt-compile-no-march" builds is good to work!
Any clue of problem?
Thanks to @gator96100 , you sir is awesome!

gator96100 · 2017-06-19 13:43:52

It seems the problem is related to qt and Intel ultra-low-power CPUs, although I doubt that the i5-5200U doesn't support the full x86_64 instruction set.
Please test what additional qt libraries are required by deleting one dll at a time out of the platforms folder and check if the client crashes.

Threshold · 2017-06-19 15:27:48

gator96100 wrote:

It seems the problem is related to qt and Intel ultra-low-power CPUs, although I doubt that the i5-5200U doesn't support the full x86_64 instruction set.
Please test what additional qt libraries are required by deleting one dll at a time out of the platforms folder and check if the client crashes.

Well , in your normal iceman builds, the "lf search" command crash too,just like "hw tune". But "hf search" won't.

I test it on "pm3-iceman-add-qt-compile-no-march" by following your instructions: I delete *.dll one by one in "platforms" folder,It seems just need "qwindows.dll". when i delete "qwindows.dll",it will crash on start up.
Sorry to bother you so much.

gator96100 · 2017-06-19 16:11:24

This doesn't make sense "iceman-no-march" should work too. “iceman-add-no-march” and “iceman-no-march” are the same. Are you sure "iceman-no-march" doesn’t work, if it doesn’t work I have made a mistake somewhere in my naming scheme.

Threshold · 2017-06-19 16:36:01

gator96100 wrote:

This doesn't make sense "iceman-no-march" should work too. “iceman-add-no-march” and “iceman-no-march” are the same. Are you sure "iceman-no-march" doesn’t work, if it doesn’t work I have made a mistake somewhere in my naming scheme.

Sorry,my mistake, I check it all over these builds again,the "iceman-no-march" builds work too.
In conclusion: "iceman-easy" "iceman-test" "iceman-no-march" "pm3-iceman-add-qt-compile-no-march" "pm3-iceman-add-no-march" these builds is good to work.

gator96100 · 2017-06-19 17:52:11

Now it makes sense again, there is a problem with compiler optimization on intel ultra-low-power CPUs. I am not sure how to properly fix this. Upgrading gcc in my ProxSpace env might solve this problem. Compiling without optimization would result in a slow hardnested attack. Not sure if @iceman plans to port the new hardnested into his fork, this would also remove the need to compile with optimizations.

Threshold · 2017-06-20 10:25:06

@gator96100 Well,It seems hard to solve the problem.
In your next iceman builds, could you please provide 2 version: one for optimization and the other is not.
Before the problem solved, I would stay on no optimization build. If someday hardnested efficiency solved, no need for two version.
Thanks for your effort!

Last edited by Threshold (2017-06-20 10:26:48)

Threshold · 2017-06-22 02:25:44

gator96100 wrote:

Now it makes sense again, there is a problem with compiler optimization on intel ultra-low-power CPUs. I am not sure how to properly fix this. Upgrading gcc in my ProxSpace env might solve this problem. Compiling without optimization would result in a slow hardnested attack. Not sure if @iceman plans to port the new hardnested into his fork, this would also remove the need to compile with optimizations.

You might be right. I test the normal iceman build on my old computer which it cpu is i5-2557M ,it works perfectly.

iceman · 2017-06-22 07:47:55

At the moment I recommened v3.0.1 or lastest source from GitHub for PM3 Master. The icemanfork is on hold for the moment

Proxmark3 community

Announcement

#1 2017-05-31 08:20:58

iceman's latest firmware crashes using both mingw and Gator.

#2 2017-05-31 08:27:42

Re: iceman's latest firmware crashes using both mingw and Gator.

#3 2017-05-31 09:24:55

Re: iceman's latest firmware crashes using both mingw and Gator.

#4 2017-05-31 12:16:31

Re: iceman's latest firmware crashes using both mingw and Gator.

#5 2017-06-01 01:01:11

Re: iceman's latest firmware crashes using both mingw and Gator.

#6 2017-06-01 03:32:18

Re: iceman's latest firmware crashes using both mingw and Gator.

#7 2017-06-01 11:45:10

Re: iceman's latest firmware crashes using both mingw and Gator.

#8 2017-06-01 13:13:58

Re: iceman's latest firmware crashes using both mingw and Gator.

#9 2017-06-01 14:01:43

Re: iceman's latest firmware crashes using both mingw and Gator.

#10 2017-06-01 15:35:59

Re: iceman's latest firmware crashes using both mingw and Gator.

#11 2017-06-03 00:46:42

Re: iceman's latest firmware crashes using both mingw and Gator.

#12 2017-06-03 11:30:42

Re: iceman's latest firmware crashes using both mingw and Gator.

#13 2017-06-03 12:49:04

Re: iceman's latest firmware crashes using both mingw and Gator.

#14 2017-06-03 17:43:45

Re: iceman's latest firmware crashes using both mingw and Gator.

#15 2017-06-03 17:46:40

Re: iceman's latest firmware crashes using both mingw and Gator.

#16 2017-06-03 17:52:27

Re: iceman's latest firmware crashes using both mingw and Gator.

#17 2017-06-18 08:57:34

Re: iceman's latest firmware crashes using both mingw and Gator.

#18 2017-06-18 13:05:02

Re: iceman's latest firmware crashes using both mingw and Gator.

#19 2017-06-18 13:05:38

Re: iceman's latest firmware crashes using both mingw and Gator.

#20 2017-06-18 14:06:24

Re: iceman's latest firmware crashes using both mingw and Gator.

#21 2017-06-18 15:10:57

Re: iceman's latest firmware crashes using both mingw and Gator.

#22 2017-06-19 02:08:22

Re: iceman's latest firmware crashes using both mingw and Gator.

#23 2017-06-19 13:43:52

Re: iceman's latest firmware crashes using both mingw and Gator.

#24 2017-06-19 15:27:48

Re: iceman's latest firmware crashes using both mingw and Gator.

#25 2017-06-19 16:11:24

Re: iceman's latest firmware crashes using both mingw and Gator.

#26 2017-06-19 16:36:01

Re: iceman's latest firmware crashes using both mingw and Gator.

#27 2017-06-19 17:52:11

Re: iceman's latest firmware crashes using both mingw and Gator.

#28 2017-06-20 10:25:06

Re: iceman's latest firmware crashes using both mingw and Gator.

#29 2017-06-22 02:25:44

Re: iceman's latest firmware crashes using both mingw and Gator.

#30 2017-06-22 07:47:55

Re: iceman's latest firmware crashes using both mingw and Gator.

Board footer