Backtrace for crash is incomplete on ARM but complete on X86

[dboothbynh]

The "backtrace" shown for a crash is truncated on ARM, but complete on X86.

I have a test program called CrashTest that has the following execution path:

main --> One --> Two --> Three

And in the "Three" function, a crash is generated, by attempting to write to memory location 0x00000001.

I build the program with Visual Studio 2017, with /MAP to generate a map file.

When I run this program under WINE on an X86 processor, with Debian 9 running on Oracle VM VirtualBox,
I get a complete backtrace that agrees with the map:

Backtrace:
=>0 0x00401036 EntryPoint+0xffffffff() in crashtest (0x0032fe50)
1 0x0040104f EntryPoint+0xffffffff() in crashtest (0x0032fe5c)
2 0x0040101e EntryPoint+0xffffffff() in crashtest (0x0032fe6c)
3 0x0040100a EntryPoint+0xffffffff() in crashtest (0x0032fe78)
4 0x00401213 EntryPoint+0xffffffff() in crashtest (0x0032fec0)
5 0x7b463532 call_process_entry+0x11() in kernel32 (0x0032fed8)
6 0x7b465682 ExitProcess+0x2141() in kernel32 (0x0032ffd8)
7 0x7b46353e call_process_entry+0x1d() in kernel32 (0x0032ffec)

But when I run it under WINE on an ARM processor, with Debian 9,
I get an incomplete backtrace:

Backtrace:
=>0 0x0040104e EntryPoint+0xffffffff() in crashtest (0xb641fdc0)
1 0x00401075 EntryPoint+0xffffffff() in crashtest (0xb641fdc0)

Why is less backtrace info shown on ARM, compared to X86?

Attached files:
* the src folder contains the source code and Visual Studio 2017 project file
* the arm and x86 folders each contain the program file, the map file, and the crash dump output for each platform.