search

jirentabu / crashrpt

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

crash reports are not saved if user presses "close the program" #63

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
***NOTE*** Please do create a NEW issue per each detected bug! Do not list
all detected problems in single issue record!

What steps will reproduce the problem?
1.cause a crash
2.click "close the program"

What is the expected output?
that it would go into the "UnsentCrashReports" folder

What do you see instead?
what was temporarily in the "UnsentCrashReports" gets deleted immediately

What version of the product are you using?
1.2.7_r997

On what operating system?
Windows 7 64bit

Original issue reported on code.google.com by anbaricf...@gmail.com on 15 Oct 2010 at 3:34

GoogleCodeExporter commented 9 years ago 
This is expected behavior, not a bug. The default behavior when user clicks the 
"Close the program" button is to close the program and delete temporary files.

If you wish that error reports to be stored locally without sending or to be 
queued for postponed delivery, use CR_INST_DONT_SEND_REPORT or 
CR_INST_SEND_QUEUED_REPORTS flags. See this page for more info on flags 
http://crashrpt.sourceforge.net/docs/html/struct_c_r___i_n_s_t_a_l_l___i_n_f_o_w
.html

Original comment by zexspect...@gmail.com on 15 Oct 2010 at 12:47

GoogleCodeExporter commented 9 years ago 
Not a bug, I think. I would close the issue if you are not against.

Original comment by zexspect...@gmail.com on 20 Oct 2010 at 1:35

GoogleCodeExporter commented 9 years ago 
no, i need the user to have discretion here.  what if they are not connected to 
the network when the crash happens?  save the report for later when they are 
connected MUST be an option.

Original comment by anbaricf...@gmail.com on 20 Oct 2010 at 6:52

GoogleCodeExporter commented 9 years ago 
Consider using CR_INST_DONT_SEND_REPORT flag. Does this works for you?

Original comment by zexspect...@gmail.com on 21 Oct 2010 at 1:33

GoogleCodeExporter commented 9 years ago 
Sorry, the correct flag is CR_INST_SEND_QUEUED_REPORTS

Original comment by zexspect...@gmail.com on 21 Oct 2010 at 1:34

GoogleCodeExporter commented 9 years ago 
but that's chicken and egg.  if you don't SAVE the reports to be queued, then 
"sending queued reports" has no queued reports to send.

i'm asking you to SAVE the reports when the user hits cancel or is offline.

Original comment by anbaricf...@gmail.com on 21 Oct 2010 at 5:28

GoogleCodeExporter commented 9 years ago 
It saves them. Just run the CrashRptTest.exe demo, generate crash reports 
several times and see how that works.

Original comment by zexspect...@gmail.com on 22 Oct 2010 at 12:48

GoogleCodeExporter commented 9 years ago 
so are you saying that, if i set this flag, then if the user hits cancel or is 
offline, then the crash report WILL be saved in the "unset reports" folder?

keep in mind i DO NOT WANT the report to be automatically sent or even ask to 
be sent on startup.  that is why this is so confusing, the flag does not 
describe what i am asking for.  like i want a flag 
"CR_INST_SAVE_UNSENT_REPORTS".  I don't want them to be sent until the user 
picks "send crash report" from the help menu.

Original comment by anbaricf...@gmail.com on 22 Oct 2010 at 3:53

GoogleCodeExporter commented 9 years ago 
I'm not sure user will ever open the Help menu to send pending error reports. I 
like the current implementation, when user is notified automatically on program 
start up. I do not plan to change the current implementation.

Original comment by zexspect...@gmail.com on 22 Oct 2010 at 2:57