jirentabu / crashrpt

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

VS 2010 project and throw tests #35

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Attached there is a patch that have 2 things:

1. Projects for VS 2010. These assume WTL80 is installed in the same folder 
as crashrpt, ('crashrpt\src\WTL80\include' exits). It is needed because in vs 
2010 (the beta at least) the include settings for VC++ are per project too.

2. 3 new crash types for crEmulateCrash: one that throws an uncaught 
exception, one that rethrows it and one that catchs it. The last one is more 
like a test that this lib does not do something in that case.

Thanks,
Pescuma

Original issue reported on code.google.com by pescuma on 1 May 2010 at 5:32

Attachments:

GoogleCodeExporter commented 9 years ago
1. Why do one needs special project files for VS 2010? It should possible to 
convert
vs2005 project files to vs2010.  

2. I do not understand what is .patch file and how I can use it. Can you 
provide your
code in text form?

Original comment by zexspect...@gmail.com on 3 May 2010 at 11:13

GoogleCodeExporter commented 9 years ago
> 1. Why do one needs special project files for VS 2010? It should possible to 
convert vs2005 project files to vs2010.  

I started converting the vs2008 solution, but it did not compile and I had to 
make 
some changes to the project files. that's why I sent them you.

> 2. I do not understand what is .patch file and how I can use it. Can you 
provide 
your code in text form?

It's a simple way to send code differences. If you use TortoiseSVN, there is an 
option "Apply patch...". Tonight I'll attach the original files too.

Original comment by pescuma on 3 May 2010 at 4:30

GoogleCodeExporter commented 9 years ago

Original comment by pescuma on 3 May 2010 at 11:52

Attachments:

GoogleCodeExporter commented 9 years ago
I tried to compile CrashRpt v.1.2.3 under VC++ 2010 Express. I think the 
currently
available VC++ version is too unstable to use. I saw too many stupid bugs. 
Project
conversion wizard seems to not work properly, compiler seems to not compile at 
all. I
would wait for more stable build of Visual C++ Express (maybe for the first 
Service
Pack).

Original comment by zexspect...@gmail.com on 4 May 2010 at 8:46

GoogleCodeExporter commented 9 years ago
I used the beta and the project compiled fine once I've made some changes to 
the 
project. Anyway, no problem, I just sent the files to you in case you wanted 
them. 

Original comment by pescuma on 4 May 2010 at 1:39

GoogleCodeExporter commented 9 years ago
What makes you use beta? Isn't it more flexible to use VS2008 with service pack?

I think that when VC++ 2010 Express becomes more stable, no changes will be 
needed in
project files. I don't like the perspective of maintaining project files for all
versions of VS, it would take too much efforts. 

Original comment by zexspect...@gmail.com on 4 May 2010 at 2:34

GoogleCodeExporter commented 9 years ago
> What makes you use beta? Isn't it more flexible to use VS2008 with service 
pack?
I installed it to test the new features,and didn't bother installing the 
express 
latter

> I think that when VC++ 2010 Express becomes more stable, no changes will be 
needed 
in project files. I don't like the perspective of maintaining project files for 
all 
versions of VS, it would take too much efforts. 
Ok

On another matter, I tested the exception buttons (that I created) in a project 
built 
using vs2008, with /EHa and /DEBUG and crashrpt does not handled the unhandled 
or 
rethrown exceptions. Do you have any idea why?

Original comment by pescuma on 4 May 2010 at 2:52

GoogleCodeExporter commented 9 years ago
I ran the same test and it handles those exceptions. Did you run your 
application
under the VS debugger? If so, run it without the debugger and see if the 
exception is
not catched. Also, compile the app in Release mode and perform the same test.

Original comment by zexspect...@gmail.com on 5 May 2010 at 11:42

GoogleCodeExporter commented 9 years ago
Fixed in v.1.2.6

Original comment by zexspect...@gmail.com on 9 Jul 2010 at 5:04