Division By Zero: 1 (Post Mortem)

Based on just this you might say, well, hey, I've got somewhat of a definition for 1 divided by 0. Maybe we can say that 1 divided by 0 is positive infinity. As we get smaller and smaller positive numbers here, we get super super large numbers right over here. But then, your friend might say, well, that worked when we divided by positive numbers close to zero but what happens when we divide by negative numbers close to zero?

So lets try those out. Well, 1 divided by negative 0.

And, if we go all the way to 1 divided by negative 0. So you when we keep dividing 1 by negative numbers that are closer and closer and closer and closer to zero, we get a very different answer.

• O Jerusalem (A Mary Russell & Sherlock Holmes Mystery Book 5)!
• Sense & Sensibility: With an Introduction by Joanna Trollope.
• Serpientes en el paraíso.
• Why dividing by zero is undefined (video) | Khan Academy!
• Why dividing by zero is undefined?

We actually start approaching negative infinity. So over here we said maybe it would be positive infinity, but you can make an equally strong argument that it could be a very different number. Negative infinity is going the exact opposite direction. So you could make an equally strong argument that it should be negative infinity. And this is why mathematicians say there's just no good answer here.

Especially one that's consistent with the rest of mathematics. They could have just said it's equal to 42 or something like that. I'm not sure how you're getting your information that a divide by zero is occurring, but if it's because the runtime is spitting out a message to that effect, you always have the option of finding out where that is handled in the runtime, and replacing it with your own more informative message.

However, I'd guess that there's a more 'architected' way to get your code to run a signal handler or ARM's technique. You should use this as an excuse to invest in improving the debug-ability of your device - for both this problem and future issues. Even if you can't get live debugging, you should be able to find a way to generate and save off core dumps for post-mortem debugging pinpointing the source or any unhandled exception immediately. It is a commercial product but there is a 30 money back guarantee. Usually the exception will be handed a structure that contains the address that caused the exception and other information.

You will probably have to become familiar with the microcontroller's datasheet or RTOS manual. Use the -save-temps for gcc and find the relevant assembly for division in the generated.

If you're lucky it will be something fairly distinctive, possibly even a function call. If it's a function call you can use weak linking to override it with your own checked version. The exception already has the address location of the offending divide by zero code. Your OS should pass this information along I assumes that is how you know it is divide by zero.

Print the address and go look in your code. If you can print a stack trace it would be even easier to solve. Another option would be to check the differences in your version control software between the last know working version and the first non working version. This should give you a limmited change set within which to search for the problem.

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service , privacy policy and cookie policy , and that your continued use of the website is subject to these policies. Finding division by zero in a big project Ask Question. Below is the information that should be present in these notices. It is designed to make submitting notices of alleged infringement to us as straightforward as possible while reducing the number of notices that we receive that are fraudulent or difficult to understand or verify.

To report this review as inappropriate, please complete this short form.

Copyright Office website, http: To file a notice of infringement with us, you must provide us with the items specified below. Please note that you will be liable for damages including costs and attorneys' fees if you materially misrepresent that the material is infringing your copyright. Accordingly, if you are not sure whether material infringes your copyright, we suggest that you first contact an attorney.

This notice and any attachments we receive will be forwarded to the alleged infringer, who will then have the opportunity to file a counter notification pursuant to Sections g 2 and 3 of the DMCA. Should a properly filed counter notification be filed, you will be notified and have 10 business days within which to file for a restraining order in Federal Court to prevent the reinstatement of the material.

All required fields must be filled out for us to be able to process your form. We help people distribute information and art spanning a wide range of subject matter while providing a safe, friendly, respectful, and serious site for all content creators. Since our community serves a broad range of ages, we do not encourage content that could make a majority of our users uncomfortable.

If you are sure that this product is in violation of acceptable content as defined in the agreement or that it does not meet our guidelines for General Access, please fill out the form below. It will then be reviewed by Lulu Staff to determine the next course of action. Identify in sufficient detail the copyrighted work that you believe has been infringed upon for example, "The copyrighted work at issue is the image that appears on http: Identify each web page that allegedly contains infringing material.

This requires you to provide the URL for each allegedly infringing result, document or item. I have a good faith belief that use of the copyrighted materials described above as allegedly infringing is not authorized by the copyright owner, its agent, or the law. I swear, under penalty of perjury, that the information in the notification is accurate and that I am the copyright owner or am authorized to act on behalf of the owner of an exclusive right that is allegedly infringed.