anerjan / asmprofiler

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

Invalid floating point operation #2

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Set up a program with fair amount of computations
2. Start profiling

What is the expected output? What do you see instead?
It should run and show the profiling results. Instead I get a "invalid 
floating point operation". My stacktrace have 6 references to 02c52d70 in 
AsmProfiler before it triggers a floating point exception in my code.

What version of the product are you using? On what operating system?
Windows XP

Please provide any additional information below.
It triggers at the same position each time, but at different cycles 
depending on if I delay it some with some breakpoints etc.

Original issue reported on code.google.com by atle.sme...@gmail.com on 30 Apr 2009 at 8:59

GoogleCodeExporter commented 8 years ago
Looks like some race condition..

Original comment by atle.sme...@gmail.com on 30 Apr 2009 at 9:04

GoogleCodeExporter commented 8 years ago
When I take away the problem area from the profiling, I get an access violation 
instead. And when trying to look at the report I get out of memory. It doesn't 
seem 
to handle hard computations with many calls?

This profiler would be great if it worked.

Original comment by atle.sme...@gmail.com on 30 Apr 2009 at 9:20

GoogleCodeExporter commented 8 years ago
Sorry for late response, Google does not automatically send emails for new 
issues. 

Is it still an issues, also with last version?
Can you send me a demo program to reproduce?

Original comment by andre.mussche on 15 Mar 2011 at 8:42

GoogleCodeExporter commented 8 years ago
Andre,

(Happy new year btw :) )

This might be an issue if COM is used with detouring.
It would be nice to have a feature to disable floating point exceptions.

Original comment by thaddyde...@gmail.com on 18 Jan 2012 at 10:49

GoogleCodeExporter commented 8 years ago
"It would be nice to have a feature to disable floating point exceptions."
I do nothing with floating point stuff like Set8087CW etc.
But you can do it yourself: http://www.neugls.info/?p=116

Original comment by andre.mussche on 27 Feb 2012 at 9:56