Debugging

  • Thread starter Thread starter Cynthia
  • Start date Start date
C

Cynthia

What is a bug, what does it do to your computer and how
do you do a debug? How often should you debug?
Thank you for your help.
 
A bug is an error in the program. Bugs are fixed by programmers employed by
the software creator, not the end user (us).

Microsoft makes their bug fixes, or "patches", available through windows
update.

You may be thinking of defragmenting your hard drive, which is a different.
Go to Start, All Programs, Accessories, System Tools, Disk Defragmenter.

Matthew
 
Cynthia said:
What is a bug, what does it do to your computer and how
do you do a debug? How often should you debug?
Thank you for your help.

A bug is a defect, often a problem that arises under a particular set of
circumstances. The term itself comes from the 1940's when computers were
large and used vaccuum tubes; because of the heat they generally ran at
night. They also attracted insects, which would fry in the circuitry.
This required debugging in a quite literal sense, and the term stuck.
IIRC, the term was actually coined by Rear Admiral Grace Hopper.

Current formal debugging often requires special versions of the software in
question (and perhaps Windows itself). These 'debug' versions have full
symbol tables so that an external program, called a debugger, can keep track
of what's happening where in the program execution. Usually you can step
through it as well. These versions are usually not available to the
general public, as they are very close to source code, aside from being
highly technical.

A more general or casual form of debugging is really careful observation and
testing to determine the full circumstances under which the problem
develops. This includes the hardware installed, the full system
configuration, installed programs, running programs, running services,
memory load, disk condition, etc. This can lead to either a solution (a
genuine fix) or a workaround (an arrangement under which the defect does not
manifest).

You generally need to engage in a debug if you are running (or writing) a
program that fails. There's no other occasion under which it's necessary.
You can *test* a properly operating system (to ensure that it WILL operate
properly), but you can only *debug* one that is failing in some way.
Software houses often run "bughunts" during development, in which a larger
group of people hammer on an in-progress work to try to find defects in a
short period of time.

You may be seeing the debug messages from the Java console or HTML pages.
Generally, you don't have a lot of opportunity to fix the defects that
invoke these messages (unless you're writing the code or simply need to
update yoru browser), so you can turn off the debug function in the browser.

HTH
-pk
 
-----Original Message-----


A bug is a defect, often a problem that arises under a particular set of
circumstances. The term itself comes from the 1940's when computers were
large and used vaccuum tubes; because of the heat they generally ran at
night. They also attracted insects, which would fry in the circuitry.
This required debugging in a quite literal sense, and the term stuck.
IIRC, the term was actually coined by Rear Admiral Grace Hopper.


The term "bug" as used in this sense predates the computer
age by at least 50 years or so it's impossible that it
could have been coined by Hopper. Also, the moths-in-the-
circuitry thing is completely apocryphal
 
Matthew said:
My, my. Those folks at the Smithsonian must be real pushovers :-)

http://americanhistory.si.edu/csr/comphist/objects/bug.htm

Matthew


Right, the moth is historical, but Grace Hopper in calling it the
first computer "bug", was using a term that had been used by
electricians for many years previously. It may well have been the
first use of the term in connection with computers, but it was
certainly not the first use of the term to describe a technical
problem.
 
-----Original Message-----
My, my. Those folks at the Smithsonian must be real pushovers :-)

http://americanhistory.si.edu/csr/comphist/objects/bug.htm

Matthew

I stand by the original statement. The information you
cite does not provide any evidence that the usage of
"bug" and "debug" was a *result* of the moth incident. All
it says is that a moth was found and taped into a log book
along with a tongue-in-cheek comment about the writer
having found a bug. It should also be noted that there is
no evidence that the moth in question actually caused any
problems; the guy found it and made a joke--a joke that
would not have made any sense had the idea of "bug" in the
sense of a glitch or problem not already existed.

BTW, it's not very likely that a moth, or even a bunch of
moths, would cause failure in an electronic device. They're
not very good conductors.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top