Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Crash report] w7 qBT v3.3.4 #3 #5279

Closed
wind77 opened this issue May 21, 2016 · 4 comments
Closed

[Crash report] w7 qBT v3.3.4 #3 #5279

wind77 opened this issue May 21, 2016 · 4 comments
Labels

Comments

@wind77
Copy link

wind77 commented May 21, 2016

qBittorrent version: v3.3.4
Libtorrent version: 1.0.8.0
Qt version: 5.6.0
Boost version: 1.60.0
OS version: Windows 7 6.1.7601 x86_64

#  0 qbittorrent.exe      0x000000000037a78f boost::asio::ssl::context::impl()
#  1 qbittorrent.exe      0x000000000037ccc9 boost::asio::ssl::context::impl()
#  2 qbittorrent.exe      0x0000000000b6ab78 boost::asio::ssl::detail::engine::write()
#  3 qbittorrent.exe      0x0000000000b515ef boost::asio::ssl::detail::engine::write()
#  4 kernel32.dll         0x00000000753f338a BaseThreadInitThunk()
#  5 ntdll.dll            0x0000000076fd9902 RtlInitializeExceptionChain()
#  6 ntdll.dll            0x0000000076fd98d5 RtlInitializeExceptionChain()
@sledgehammer999
Copy link
Member

Unfortunately these backtraces aren't helpful. The crash probably happens in another place and a debugger would help find the correct place. Since you get them quite often do you care helping a bit more?

  1. Go here. Scroll down to "Debugging Tools for Windows 10 (WinDbg)". Select "Get Debugging Tools for Windows (WinDbg) (from the SDK)". It is a "downloading" setup. Choose to install Windbg. If it lets you install 32bits.
  2. Open Windbg (the 32 bits variant)
  3. File->Symbol File Path... and then input srv*c:\mss*http://msdl.microsoft.com/download/symbols
  4. File->open executable...
  5. Choose the qbittorrent.exe
  6. Debug->Go
  7. You'll see some output in the "Command" subwindow. Wait until qbt crashes. Don't worry if you need to run through WinDbg for extended periods of time. Nothing bad can happen. Also if qbt crashes, the debugger will most probably freeze the qbt window. So don't freak out if it stops responding. Just follow the next step.
  8. Now you should be able to input commands in the bottom of the "Command" subwindow.
  9. Issue: |* ~* kp
  10. Issue: |* !analyze -v -f
  11. Issue: |* lm

After that paste the output here or on pastebin.com(with a link here).
The stacktrace will hopefully show me what is wrong.

@Misiek304
Copy link

@sledgehammer999 - Your instructions are for Windows 10, but @wind77 has Windows 7. Can this instruction be applicable also on Win7?

@sledgehammer999
Copy link
Member

Yes the debugger should work on windows 7 too.

@ngosang
Copy link
Member

ngosang commented Sep 16, 2018

We are closing all issues related to old qBittorrent versions (qBittorrent < 4.1.0).
Please, update to last release and, if the bug/error/crash is still present, open another issue.
Thank you.

@ngosang ngosang closed this as completed Sep 16, 2018
@qbittorrent qbittorrent locked and limited conversation to collaborators Feb 28, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants