PR# 16772 Disabling assertion monitoring has no effect?

Problem Report Summary
Submitter: manus_eiffel
Category: EiffelStudio
Priority: Medium
Date: 2010/05/20
Class: Bug
Severity: Serious
Number: 16772
Release: 6.6.8.3200
Confidential: No
Status: Analyzed
Responsible:
Environment: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.38 Safari/533.4
Synopsis: Disabling assertion monitoring has no effect?

Description
See the attached picture. At the very beginning of the program, I've disabled assertion monitoring (you see the button pressed in the toolbar). However I'm still getting a precondition violation which is definitely not expected.
To Reproduce

										

									

								

							

						

					

				

			

		

	









	

		

			
Problem Report Interactions

			

				

					
					

						

							
							

								

									
									
										

											

									
											From:manus_eiffel   
											Date:2010/05/21   
											
											Download   
										

										

                                            
											
										 	
This is exactly what I've done. To reproduce is to take the revision of the compiler from 2 days ago and compile eweasel test#exec325 and then you get the precondition violation when you should not.

											
											
											

											
										

									

								

							

							
							

								

									
									
										

											

									
											From:jfiat_es   
											Date:2010/05/21   
																							Status: Analyzed   
											
											Download   
										

										

                                            
											
										 	
When you say at the beginning ...
you did "step into" to launch the application, and then "Disable assertion" ?

I've just tried, and this works for my test.

But if you "Disable assertion" when you are in assertion (and also in rescue I think), it will be reset internally.

Same issue with {ISE_RUNTIME}.check_assert (b: BOOLEAN): BOOLEAN

But if you disable assertion right away when you start execution ...
this should be disabled.

If not, can you indicate how to reproduce?


											
											
											

											
										

									

								

							

							
							

								

									
									
										

											

									
											From:manus_eiffel   
											Date:2010/05/20   
											
											Download   
										

										

                                            
											
										 	
Attachments for problem report #16772

											
											
											

											
											

												

													

														

															Attachment:
															disable_assertion_monitoring_failure.png    
															Size:165763