bench failed on Windows #37

Activity

1. tarcieri

   changed the title [-]bench failed[/-] [+]bench failed on Windows[/+] on Jun 15, 2021
2. tarcieri commented on Jun 15, 2021

   

   tarcieri

   on Jun 15, 2021

   Member

   More actions

   Hmm, I'm not quite sure what's happening there. While we do have CI for those environments, we don't test the benchmarks, nor do I have access to a Windows machine to confirm myself.

   I've never seen "bench failed" before. Is it panicking?

   Can you try going into the individual directories and running the benchmarks? It looks like md5-asm is failing there, but do the other benchmarks fail in the same way if you run them individually?
3. chawyehsu commented on Jun 15, 2021

   

   chawyehsu

   on Jun 15, 2021

   Author

   More actions

   @tarcieri Unfortunately, I ran them individually and all of them fail with the same error and no other output. The build is successful, but I don't know it's panicking or not since the only message I can see is the one of error: bench failed.
4. tarcieri commented on Jun 15, 2021

   

   tarcieri

   on Jun 15, 2021

   Last edited by tarcieri

   Member

   More actions

   Wow, that's really confusing.

   Can you try running the binary under a debugger like gdb? Something like:

   $ gdb C:\workspace\repos\github.com\RustCrypto\asm-hashes\target\release\deps\lib-dab98c6ec0ebcfb5.exe
   (gdb) run --bench
   
5. chawyehsu commented on Jun 15, 2021

   

   chawyehsu

   on Jun 15, 2021

   Last edited by chawyehsu

   Author

   More actions

   (gdb) run --bench
   Starting program: C:\workspace\repos\github.com\RustCrypto\asm-hashes\target\release\deps\lib-be2dc135b8dd9613.exe --bench
   [New Thread 5852.0x4c18]
   [New Thread 5852.0x8688]
   [New Thread 5852.0x5fe0]
   
   running 1 test
   
   Thread 1 received signal SIGSEGV, Segmentation fault.
   0x00007ff6dcb61f1d in md5_compress ()
   (gdb) info registers
   rax            0x1fe64             130660
   rbx            0x8b741fe6a0        598948701856
   rcx            0x8b741fe6a0        598948701856
   rdx            0x11034064          285425764
   rsi            0x7d0               2000
   rdi            0x11034064          285425764
   rbp            0x7d0               0x7d0
   rsp            0x8b741fe2a8        0x8b741fe2a8
   r8             0xff                255
   r9             0x7ffee000          2147409920
   r10            0x1                 1
   r11            0x467e00b301        302761685761
   r12            0x8b741fe3e0        598948701152
   r13            0x8b741fe370        598948701040
   r14            0x8b741fe3e8        598948701160
   r15            0x8b741fe300        598948700928
   rip            0x7ff6dcb61f1d      0x7ff6dcb61f1d <md5_compress+13>
   eflags         0x10206             [ PF IF RF ]
   cs             0x33                51
   ss             0x2b                43
   ds             0x2b                43
   es             0x2b                43
   fs             0x53                83
   gs             0x2b                43
6. tarcieri commented on Jun 15, 2021

   

   tarcieri

   on Jun 15, 2021

   Member

   More actions

   Okay, that's helpful! Can you run info registers?
7. chawyehsu commented on Jun 15, 2021

   

   chawyehsu

   on Jun 15, 2021

   Author

   More actions

   I edited the comment and added the info.

   👍React with 👍1Reacted by Tony Arcieri
8. tarcieri commented on Jun 15, 2021

   

   tarcieri

   on Jun 15, 2021

   Member

   More actions

   Thanks! I'll try to look into this a bit more when I have time, but it seems like the kind of problem where I might need to set up a Windows VM to debug.

   Really we should probably just switch to better assembly implementations (see #5)

   👍React with 👍1Reacted by Chawye Hsu
9. newpavlov

   closed this as completedin #79on May 7, 2024