search

jirentabu / crashrpt

Automatically exported from code.google.com/p/crashrpt
0 stars 0 forks source link

CrashSender crashes (!) (lol) #32

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. compile your app (possibly relevant: under parallels, using a mapped
".psf" network drive to access files on the mac HFS+ drive)
2. run
3. purposely crash the app

What is the expected output?
--> crash reporter comes up

What do you see instead?
--> crash does not come up, instead i get a dialog saying "crash sender
failed".  Shouldn't the reporter come up before the sender even runs?

What version of the product are you using?
--> 1.2.2

On what operating system?
Win Vista 64 Enterprise, running under Parallels 5.0.9344 rev 558741 on
MacOS 10.6.3 build 10D573

Please provide any additional information below.
    info.uPriorities[CR_SMAPI] = 3;
    info.uPriorities[CR_SMTP] = 2; 
    info.uPriorities[CR_HTTP] = 1;
i tried turning off "managed code" for crash sender with:

"C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\bin\editbin.exe"
/NXCOMPAT:NO "../build/kJamsX Pro Debug.app/Contents/Windows/CrashSender.exe"

but that did not help

Original issue reported on code.google.com by anbaricf...@gmail.com on 17 Apr 2010 at 9:54

Attachments:

GoogleCodeExporter commented 9 years ago 
There is too few information in your description. Can you provide the complete 
code
of how you fill the CR_INSTALL_INFO and how you call crInstall()? There may be 
other
affecting factors, such as location of dbghelp.dll and CrashSender.exe.

It would be the best if you run CrashSender under debugger to determine the 
place in
code that causes crash. To do this, use Visual Studio to attach to 
CrashSender.exe in
debug mode.

Original comment by zexspect...@gmail.com on 18 Apr 2010 at 2:38

GoogleCodeExporter commented 9 years ago 
Btw, the latest version is v1.2.3. You use v1.2.2. Please upgrade. This may fix 
your
problem.

Original comment by zexspect...@gmail.com on 18 Apr 2010 at 12:31

GoogleCodeExporter commented 9 years ago 
you may close this bug, the latest version has fixed it, thank you, you guys are
totally on top of this!

-dave

Original comment by anbaricf...@gmail.com on 18 Apr 2010 at 6:29

GoogleCodeExporter commented 9 years ago 
Closed. The problem seems to be fixed in v1.2.3.

Original comment by zexspect...@gmail.com on 19 Apr 2010 at 3:35