text:
List of Mike & Molly characters
From Wikipedia, the free encyclopedia
Jump to: navigation, search
Mike & Molly is a sitcom which premiered in September 2010. The show revolves around the lives of Mike Biggs, a police officer, and Molly Flynn, a schoolteacher, who meet at an Overeaters Anonymous meeting and fall in love. The series follows their relationship with each other and their two families.
Contents
[hide]
1 Cast
1.1 Main cast
2 Main characters
2.1 Mike Biggs
2.2 Molly Flynn
3 Supporting characters
3.1 Carl McMillan
3.2 Victoria Flynn
3.3 Joyce Flynn
3.4 Samuel
3.5 Vince Moranto
3.6 Peggy Biggs
3.7 Rosetta McMillan
3.8 Harry
4 Recurring characters
4.1 Christina
4.2 Brother Heywood
4.3 Jack Biggs
4.4 Captain Murphy
5 References
6 External links
Cast[edit]
Starring
Recurring/Guest
No appearances
Character
Season
Season 1
(2010-2011)
Season 2
(2011–2012)
Season 3
(2012–2013)
Season 4
(2013–2014)
Season 5
(2014–2015)
Season 6
(2015–2016)
Main cast[edit]
Mike Biggs
Billy Gardell
Molly Flynn
Melissa McCarthy
Carl McMillan
Reno Wilson
Victoria Flynn
Katy Mixon
Joyce Flynn
Swoosie Kurtz
Samuel
Nyambi Nyambi
Vince Moranto
Louis Mustillo
Peggy Biggs
Rondi Reed
Rosetta McMillan
Cleo King Cleo King
Harry
David Anthony Higgins David Anthony Higgins David Anthony Higgins
Main characters[edit]
Mike Biggs[edit]
Mike Biggs
First appearance
"Pilot"
1x01, September 20th, 2010
Last appearance
"I See Love"
6x13, May 16th, 2016
Portrayed by
Billy Gardell
Information
Gender
Male
Occupation
Police officer
Family
Peggy Biggs (mother)
Jack Biggs (father)
Spouse(s)
Molly Flynn
Children
William Michael Biggs (Adoptive Son)
Unborn Child (Currently Expecting with Molly)
Relatives
Joyce Flynn-Moranto (mother-in-law)
Mr Flynn (father-in-law; deceased)
Victoria Flynn (Sister-in-law)
Vincent Moranto (step-father-in-law)
Religion
Christian (Roman Catholic)
Nationality
American
Officer Michael "Mike" Biggs (Billy Gardell), is the lead male protagonist of the series. He is introduced in the first episode as a Chicago police officer with weight issues who attends a meeting of Overeaters Anonymous. It is here that he meets Molly Flynn. After Molly asks Mike to come and speak to her class at the school where she works, they begin dating in the second episode. Mike is regularly accompanied by his best friend, Carl McMillan, his partner on the police force, whom he joins for breakfast to chat about the state of their lives at a cafe where their waiter is always Samuel, an African immigrant who likes to make fun of Mike's weight. Mike and Molly got engaged in the season 1 finale, are married in the season 2 finale, and are still trying to conceive their first child as of the Season 4 premiere. In Season 5, though, Mike finds out that Molly went back on birth control without telling him due to the pain and frustration of two years when she was unable to conceive a child, and they resolve to pursue avenues like adoption as they still love each other and want to raise kids.
Molly Flynn[edit]
Molly Flynn-Biggs
First appearance
"Pilot"
1x01, September 20, 2010
Last appearance
"I See Love"
6x13, May 16, 2016
Portrayed by
Melissa McCarthy
Information
Gender
Female
Occupation
4th Grade Schoolteacher (Prior to Season 1-Season 4), Writer (Season 4-Present)
Family
Joyce Flynn-Moranto (mother)
Mr Flynn (father; deceased)
Victoria Flynn (Younger Sister)
Vince Moranto (step-father)
Spouse(s)
Mike Biggs
Children
William Michael Biggs (Adopted Son)
Unborn Child (expecting with Mike)
Relatives
Peggy Biggs (mother-in-law)
Jack Biggs (father-in-law)
Religion
Christian
Nationality
American
Molly Flynn-Biggs (Melissa McCarthy) is the lead female protagonist of the series. She is a fourth grade school teacher who attends the same Overeaters Anonymous class as Mike. She lives with her mother Joyce and her sister Victoria, while her mother's partner Vince Moranto is often seen at the house. She is very sweet, intelligent and caring, but she can be hypersensitive and has a very bad financial history thanks to a large amount of credit card debt. She and Mike married in the season 2 finale. She and Mike spent two years trying to have a child but put those plans on hold in Season 5. In Season 4, she quits her teaching job to pursue a career as a writer, and in Season 5 she has a huge success when her literary erotica novel is published by a major company. It is later revealed in a session with a psychologist that Mike's stabilizing presence, something she hasn't had since her father died, has allowed Molly to finally feel comfortable taking risks.
Melissa McCarthy won the Primetime Emmy Award for Outstanding Lead Actress in a Comedy Series in 2011 for her portrayal of Molly Flynn.
Supporting characters[edit]
Carl McMillan[edit]
Carl McMillan
First appearance
"Pilot"
1x01, September 20, 2010
Last appearance
"I See Love"
6x13, May 16, 2016
Information
Gender
Male
Occupation
Police officer
Relatives
Rosetta McMillan (maternal grandmother)
Officer Carlton "Carl" Enoch McMillan (Reno Wilson) is Mike Biggs' best friend/surrogate brother and fellow officer on the police force. He lives with his grandma until the middle of Season 3, as he has not been able or motivated to find his own place. Until the middle of Season 2, he did not have a steady girlfriend, and Mike has frequently alluded to Carl employing prostitutes or having one-night stands with strippers. He is quick-witted with a dry sense of humor, and offers droll remarks on various situations. Carl and Samuel become roommates in Season 3. After a rather depressing break up with his girlfriend Christina (she leaves him for her ex-husband), he goes through a string of random women until towards the end of season 4, when he begins relationship with Molly's sister Victoria. In an episode before the Season 5 finale, this relationship sours when Carl announces to Mike that he plans to propose to Victoria, only to change his mind. Carl then gets angry with Victoria when she is relieved that he didn't propose, and that leads to a spiral in the Season 5 finale where he has broken up with her. He ends up having a huge fight with Mike when he feels like his best friend is siding with Molly's family over him, and this ultimately leads him to request a transfer so he won't have to work with Mike anymore. Eventually they work out their differences, as both of them hate their new partners and Carl defends Mike when the other cops (including several hard-core macho officers whom they both dislike) make fun of hiim. In the final episode, it's revealed that he and Victoria were secretly fooling around the house once again, but in a conversation with Peggy he admits that all of the old feelings were resurfacing, hinting that there's a possibility that they might become a couple again.
Victoria Flynn[edit]
Victoria Flynn (Katy Mixon) is Molly's dimwitted but kind, party girl sister who is often high on marijuana. (Policemen Mike and Carl take a "don't tell, we won't ask" attitude about her drug use.) She is employed as a beautician at a funeral home. She likes to have fun and sleeps around, frequently with married men, and her combination of not being particularly bright and being a pothead leads to her often losing or misplacing major items like her car. Harry has an almost obsessive crush on her, and she has on occasion gone on dates with him just to be nice. In Season 3, she starts to realize that Harry is the only man who's ever truly cared for her, and she finally kisses him. In an odd turn of events, he then announces he's gay. As of the end of Season 4, she is in a relationship with Carl, which lasts until the penultimate episode of Season 5 when they have a bitter break up. In the series finale, it's revealed that they're sleeping together, but it is hinted that there is the possibility of it becoming more serious.
Victoria demonstrates a very kind personality consistently through the series. On the night before Mike and Molly's wedding, she has a bonding moment with Molly, telling her that she and Christina worked together and got the church and hall ready despite all the drama that took place at the rehearsal. She also gives Molly a garter to wear which she had made from one of their deceased father's blue silk ties, covering the old, new, borrowed and blue tradition all in one and stating that in a way their father would be walking down the aisle with Molly, which moved both of them to happy tears. When shown doing her job, she treats the bodies she's tasked to do the makeup on with respect and even wishes one luck on his journey to the other side. In a conversation with Mike while at work, she regretfully reveals what she had to do to make the corpse she was working on smile, which wasn't pleasant. She also reveals that she believes no matter what happens after ones dies they should look their best, demonstrating her kind personality.
Although she is generally dimwitted, high, or drunk (often all at once), Victoria is much more intelligent than other characters give her credit for. When Peggy got into a fight with Mike and announced that she would not attend his wedding because Mike was inviting his father, it was Victoria that convinced her to reconsider by pointing out how well Mike turned out because of Peggy's influence. She also pointed out that she could use the occasion to show Mike's father how well she's done since he left, the mistake he made by leaving, gave suggestions on what she could wear to the wedding to show off her legs (complimenting on how well they've held up) and even offered to help her with her makeup for the day. On another occasion Joyce revealed that she's leaving the house to Victoria in her will, irritating Molly. A drunk Molly tells Victoria that it was because Molly was Joyce's good daughter and Victoria was a mess. Victoria stood up to Molly, pointing out that she quit her teaching job (which resulted in Molly losing her pension and benefits) and was currently in severe debt due to her wild spending. She then revealed that all of her own credit cards were paid off, has never had nor ever will have any credit card debt and that she could afford a down payment on a house even if Joyce hadn't left her one. She also pointed out that at that moment she was sober and Molly was the mess before going upstairs to see how her stocks performed that day, demonstrating that she had good business sense, something Molly had no idea about (all this was true, but Joyce later told Molly in private that she knew Victoria would sell the house right after her funeral, and that she didn't want Molly to spend the rest of her life in the house when she could make a much bigger mark on the world than Joyce did).
Joyce Flynn[edit]
Joyce Marilyn Flynn-Moranto (Swoosie Kurtz) is Molly and Victoria's mother. Her two daughters live in her home. She is a widow who began dating a widower named Vince Moranto in Season 1, and later became his fiancée. She is very modern and often attempts to act or dress younger than her age, and she drinks heavily. She has a hair-trigger temper and is sometimes rude to Mike, but he doesn't seem to care and she ultimately respects that he doesn't let her get away with her worst behavior. She frequently teases Mike for his size and eating habits, even though it is revealed in multiple conversations that her late husband was also a very large man. In the Season 3 episode "Thanksgiving Is Cancelled", she marries Vince.
Samuel[edit]
Samuel (Nyambi Nyambi) is a sarcastic waiter at Abe's, where Mike and Carl eat. He is often seen hanging out with Carl and Mike, and despite frequently insulting them, he is considered their friend. He is from Africa and often refers to the suffering in his home country of Senegal (which he was apparently kicked out of[1]). As such, he does not sympathize with most problems his restaurant patrons bring to his attention, believing them to be "petty". He becomes Carl's roommate in Season 3. In Season 5, Samuel's real name is revealed to be Babatunde when he becomes the owner of Abe's Diner, now Abe's Hot Beef. He states the previous owner was so cheap he wouldn't buy him a badge with Babatunde on it, instead giving him a former employee's badge. He notes that the high cost of replacing the sign will keep the Abe's name intact until he can afford to proudly put up a sign for "Babatunde's Restaurant".
Vince Moranto[edit]
Vince Moranto (Louis Mustillo) is Joyce's on-and-off boyfriend in Season 1, who thereafter becomes her fiancé. He is a widower and tends to be chauvenistic and sarcastic, and also likes to openly discuss his sex life, one of the main reasons neither Mike nor Molly seek out his company nor spend more time around him than required. He is a high school dropout and can come across as unintelligent, though the series has shown or mentioned he had made a lot of money in the past through his various enterprises (some of which may be a bit "shady"). In the second-to-last episode of Season 2, it is revealed he is technically still married to a much older woman. (Vince claims that at the time of their marriage, the woman was "a very do-able 60-year old.") Joyce throws out Vince when she learns of the marriage at Mike & Molly's wedding rehearsal.[2] Vince actually hadn't seen the woman in several years, outside of a few attempts to get her to sign divorce papers, which she consistently refused because Vince still owes her $2,000 "plus interest." Mike negotiates with the woman to sign the divorce papers in exchange for $5,000 from Vince and the opportunity to kick Vince in the crotch. Joyce and Vince reconcile, and in the Season 3 episode "Thanksgiving Is Cancelled", they get married. In Season 5, he becomes an investor in Abe's Diner, after Samuel assumes ownership.
Peggy Biggs[edit]
Peggy Biggs (Rondi Reed) is Mike's mother. She is very controlling and traditional, as well as grumpy and cranky. Peggy frequently expects Mike to do her bidding at the drop of a hat, which made her initially cold toward Molly becoming a part of Mike's life. She has since warmed up some to Molly, and began working as a lunch lady at Molly's school in Season 2. Her tendency to lie when the truth isn't kind to her connected with that job when she told Molly she had "retired"; she'd actually been fired for being impossible to work with. Mike usually plays along with her revisionist history, but finally gets pushed too far in this case and tells Peggy she got fired because she is bitter, toxic and unlikable by anyone. She is divorced, living alone with her dog "Jim" (she even turned over Mike's old room to Jim) and often talks about her ex-husband, Jack, leaving her and running away with a "whore". Her longtime courtship of a sweet-natured and unsuccessful fellow Catholic named Dennis ended badly when she finally decided she was ready for them to have sex, only to realize he'd suffered a heart attack and died. A shocked Peggy tried to blame it on a sour lemon cake Molly had prepared for her birthday, only to have a no-longer-afraid Molly jab Peggy about her ham-fisted efforts to cover up her death-blocked seduction of Dennis. Despite her obvious disdain for Jack, the two sleep together after Mike and Molly's wedding rehearsal, but Peggy dumps him immediately after. She has a gift for writing that Molly surprisingly discovered during her own successful effort to start a career as an author, and Peggy's sordid past romantic exploits become the basis for Molly's second novel. Peggy reveals that she has always felt guilty for leaving her abusive home at an early age, while her mother was stuck with a drunken batterer for a husband. She also has a sister who still lives in their hometown with whom she has feuded since their teenage years, but they eventually reconciled in Season 5. As the series ends, Peggy remained both manipulative and decent-hearted, from playing on tension between Molly and Mike when she suffers a heart attack that Mike felt Molly caused (Peggy confirmed she didn't) and nearly getting her ass kicked by Joyce when she tries to guilt Mike into moving back home, but being reassured by Mike that while he won't move back home then or ever he still will make sure she's part of her grandchild's life.
Rosetta McMillan[edit]
Rosetta McMillan (Nana) (Cleo King) is Carl's grandmother. She apparently raised Carl since his childhood, and Carl still lives in her house. She is very traditional and has professed that Carl is a very special part of her life, but she is outwardly annoyed by his immature behavior. She has a big heart and is very friendly toward Mike, who calls her "Nana." She has been known to treat Mike as if he were also her grandson, and Mike frequently goes to Rosetta for advice about his relationship with Molly, rather than to his own mother. Despite her advancing age, she is shown to have a large sexual appetite, including an ongoing relationship with the preacher from her church. (Being only seven years older than Reno Wilson in real life, King wears a wig and makeup to appear older.)
Harry[edit]
Harry (David Anthony Higgins) attends the same Overeaters Anonymous meetings as Mike and Molly, and becomes their friend. He is depicted as socially awkward and lonely, and tends to say whatever is on his mind, even thoughts that make him seem pathetic. Harry initially pursued Victoria as a love interest. The two dated once, and while it is suggested that Victoria does so out of sympathy, they attended a few other events as friends and Harry has been visibly happy to spend time with her in any capacity. In Season 3, after he finally receives a kiss from her, he announces that he's gay (to everyone's surprise except Joyce and Carl). Vince tends to speak for the group in one sense by constantly making fun of Harry and wondering why he's invited to any of their events, while Mike responds by saying they all basically like Harry even though he can be incredibly annoying.
Recurring characters[edit]
Christina[edit]
Christina (Holly Robinson Peete) is Carl's girlfriend, beginning in Season 2. She is a single mother with a young son, and works as an optometrist. When Carl runs away from her after learning about her kid, she lets Carl know that he's a coward and loser who isn't worth her time. However, she accepts his later explanation about never knowing his father, and they become a committed couple. She later becomes Molly's friend. As of Season 3, she has decided to try and reconcile with her ex-husband for the sake of their son, and breaks things off with Carl. After Christina makes several negative remarks about Carl during a conversation with Molly, Molly drops her as a friend.
Brother Heywood[edit]
Brother Heywood (Reginald VelJohnson) is the preacher at Carl and Rosetta's church. It is strongly hinted (and later openly revealed) that he and Rosetta are in a sexual relationship. He officiated at Mike and Molly's wedding, after Molly was too honest with the priest at Mike's Catholic church and the two were forced to look elsewhere.
Jack Biggs[edit]
Jack Biggs (Francis Guinan) is Mike's father, who left Mike and his mother many years ago to run off with a woman whom Peggy simply refers to as "the whore." He first appears at Mike's bachelor party in Season 2 and tearfully apologizes to his son for running away, to which Mike honestly tells his father he loves him and is glad he will be at the wedding. After Peggy and he sleep together, he decides he wants to reconcile with her (his marriage to "the whore" is rapidly disintegrating) but Peggy bluntly says she only used him for sex and has zero interest in him now that he's served his purpose.
Captain Murphy[edit]
Captain Patrick Murphy (Gerald McRaney) is Mike's boss on the Chicago Police force. Early in Season 3, he offers Mike courtside seats at a basketball game in exchange for Mike setting him up with Peggy. Soon after, Captain Murphy and Peggy begin dating. Peggy refers to him as "Paddy", though Mike doesn't dare call him that.
References[edit]
Jump up ^ Episode 1.21: "Samuel Gets Fired"
Jump up ^ Episode 2:22: "The Rehearsal" at cbs.com
External links[edit]
Official website
List of Mike & Molly characters on IMDb
[hide]
v
t
e
Mike & Molly
Episodes
Season 1
Season 2
Season 3
Season 4
Season 5
Season 6
Related
Characters
Retrieved from "https://en.wikipedia.org/w/index.php?title=List_of_Mike_%26_Molly_characters&oldid=812251896"
Categories:
Mike & Molly
Lists of American sitcom television characters
Hidden categories:
Pages using infobox character with unknown parameters
Official website not in Wikidata
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Namespaces
Article
Talk
Variants
Views
Read
Edit
View history
More
Search
Navigation
Main page
Contents
Featured content
Current events
Random article
Donate to Wikipedia
Wikipedia store
Interaction
Help
About Wikipedia
Community portal
Recent changes
Contact page
Tools
What links here
Related changes
Upload file
Special pages
Permanent link
Page information
Wikidata item
Cite this page
Print/export
Create a book
Download as PDF
Printable version
Languages
Add links
This page was last edited on 26 November 2017, at 22:12.
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.
Privacy policy
About Wikipedia
Disclaimers
Contact Wikipedia
Developers
Cookie statement
Mobile view
Enable previews

key: html

type: local

value: div

attrs: id class

values: mw-page-base noprint

values: mw-head-base noprint

value: a

value: i

attrs: id class lang

values: firstHeading firstHeading en

values: siteSub noprint

values: jump-to-nav mw-jump

attrs: href title

attrs: href class title

values:
/wiki/Mike_Biggs
mw-redirect
Mike Biggs

values:
/wiki/Molly_Flynn
mw-redirect
Molly Flynn

attrs: role tabindex class

values: button 0 togglelink

values: border-collapse: collapse; padding: 0; border: 0; background:transparent; width:100%;

values:
/wiki/Carl_McMillan
mw-redirect
Carl McMillan

values:
/wiki/Victoria_Flynn
mw-redirect
Victoria Flynn

values:
/wiki/Joyce_Flynn
mw-redirect
Joyce Flynn

values:
/wiki/Samuel_(Mike_%26_Molly)
mw-redirect
Samuel (Mike & Molly)

values:
/wiki/Vince_Moranto
mw-redirect
Vince Moranto

values:
/wiki/Peggy_Biggs
mw-redirect
Peggy Biggs

values:
/wiki/Rosetta_McMillan
mw-redirect
Rosetta McMillan

values:
/wiki/Pilot_(Mike_%26_Molly)
mw-redirect
Pilot (Mike & Molly)

values:
infobox
width:22em;border-spacing: 2px 5px;

values:
reflist mw-references-wrap
list-style-type: decimal;

values:
nofollow
http://www.imdb.com/title/tt1608180/
external text

values: nowraplinks collapsible autocollapse navbox-inner

values: Category:Lists of American sitcom television characters

values: Category:Pages using infobox character with unknown parameters

values: Category:Official website not in Wikidata

values: Discussion about edits from this IP address [ctrl-alt-n]

values: A list of edits made from this IP address [ctrl-alt-y]

values: You are encouraged to create an account and log in; however, it is not mandatory

values: You're encouraged to log in; however, it's not mandatory. [ctrl-alt-o]

values:
/wiki/List_of_Mike_%26_Molly_characters
View the content page [ctrl-alt-c]
c

values: Discussion about the content page [ctrl-alt-t]

values: p-namespaces navigation vectorTabs p-namespaces-label

values:
p-variants
navigation
vectorMenu emptyPortlet
p-variants-label

values: Past revisions of this page [ctrl-alt-h]

values: p-views navigation vectorTabs p-views-label

values:
p-cactions
navigation
vectorMenu emptyPortlet
p-cactions-label

values:
mw-wiki-logo
/wiki/Main_Page
Visit the main page

values:
/wiki/Main_Page
Visit the main page [ctrl-alt-z]
z

values: Featured content – the best of Wikipedia

values: Find background information on current events

values:
/wiki/Special:Random
Load a random article [ctrl-alt-x]
x

values: portal navigation p-navigation p-navigation-label

values: Guidance on how to use and edit Wikipedia

values: About the project, what you can do, where to find things

values: A list of recent changes in the wiki [ctrl-alt-r]

values: portal navigation p-interaction p-interaction-label

values: List of all English Wikipedia pages containing links to this page [ctrl-alt-j]

values: Recent changes in pages linked from this page [ctrl-alt-k]

values:
/wiki/Wikipedia:File_Upload_Wizard
Upload files [ctrl-alt-u]
u

values: A list of all special pages [ctrl-alt-q]

values: Permanent link to this revision of the page

values: Link to connected data repository item [ctrl-alt-g]

values: Printable version of this page [ctrl-alt-p]

values:
uls-settings-trigger
Language settings
0
button
true

values: mediawiki ltr sitedir-ltr mw-hide-empty-elt ns-0 ns-subject page-List_of_Mike_Molly_characters rootpage-List_of_Mike_Molly_characters skin-vector action-view


text:
Software bug
From Wikipedia, the free encyclopedia
Jump to: navigation, search
To report a MediaWiki error on Wikipedia, see Wikipedia:Bug reports.
This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. (September 2017) (Learn how and when to remove this template message)
Software development
Core activities
Processes
Requirements
Design
Engineering
Construction
Testing
Debugging
Deployment
Maintenance
Paradigms and models
Agile
Cleanroom
Incremental
Prototyping
Spiral
Waterfall
Methodologies and frameworks
ASD
DevOps
DSDM
FDD
IID
Kanban
Lean SD
MDD
MSF
PSP
RAD
SAFe
Scrum
SEMAT
TSP
UP
V-Model
XP
Supporting disciplines
Configuration management
Documentation
Software quality assurance (SQA)
Project management
User experience
Practices
ATDD
BDD
CCO
CI
CD
DDD
PP
Stand-up
TDD
Tools
Compiler
Debugger
Profiler
GUI designer
Modeling
IDE
Build automation
Release automation
Infrastructure as Code
Testing
Standards and BOKs
CMMI
IEEE standards
ISO 9001
ISO/IEC standards
SWEBOK
PMBOK
BABOK
v
t
e
A software bug is an error, flaw, failure or fault in a computer program or system that causes it to produce an incorrect or unexpected result, or to behave in unintended ways. The process of fixing bugs is termed "debugging" and often uses formal techniques or tools to pinpoint bugs, and since the 1950s, some computer systems have been designed to also deter, detect or auto-correct various computer bugs during operations.
Most bugs arise from mistakes and errors made in either a program's source code or its design, or in components and operating systems used by such programs. A few are caused by compilers producing incorrect code. A program that contains a large number of bugs, and/or bugs that seriously interfere with its functionality, is said to be buggy (defective). Bugs can trigger errors that may have ripple effects. Bugs may have subtle effects or cause the program to crash or freeze the computer. Other bugs qualify as security bugs and might, for example, enable a malicious user to bypass access controls in order to obtain unauthorized privileges.
Some software bugs have been linked to disasters. Bugs in code that controls the Therac-25 radiation therapy machine were directly responsible for patient deaths in the 1980s. In 1996, the European Space Agency's US$1 billion prototype Ariane 5 rocket had to be destroyed less than a minute after launch due to a bug in the on-board guidance computer program. In June 1994, a Royal Air Force Chinook helicopter crashed into the Mull of Kintyre, killing 29. This was initially dismissed as pilot error, but an investigation by Computer Weekly convinced a House of Lords inquiry that it may have been caused by a software bug in the aircraft's engine-control computer.[1]
In 2002, a study commissioned by the US Department of Commerce's National Institute of Standards and Technology concluded that "software bugs, or errors, are so prevalent and so detrimental that they cost the US economy an estimated $59 billion annually, or about 0.6 percent of the gross domestic product".[2]
Contents
[hide]
1 Etymology
2 History
2.1 "Bugs in the System" report
3 Terminology
4 Prevention
4.1 Typographical errors
4.2 Development methodologies
4.3 Programming language support
4.4 Code analysis
4.5 Instrumentation
5 Testing
6 Debugging
7 Bug management
7.1 Severity
7.2 Priority
7.3 Software releases
8 Types
8.1 Arithmetic
8.2 Logic
8.3 Syntax
8.4 Resource
8.5 Multi-threading
8.6 Interfacing
8.7 Teamworking
9 Implications
10 Well-known bugs
11 In popular culture
12 See also
13 References
14 Further reading
15 External links
Etymology[edit]
The term "bug" to describe defects has been a part of engineering jargon since the 1870s and predates electronic computers and computer software; it may have originally been used in hardware engineering to describe mechanical malfunctions. For instance, Thomas Edison wrote the following words in a letter to an associate in 1878:
It has been just so in all of my inventions. The first step is an intuition, and comes with a burst, then difficulties arise—this thing gives out and [it is] then that "Bugs"—as such little faults and difficulties are called—show themselves and months of intense watching, study and labor are requisite before commercial success or failure is certainly reached.[3]
The Middle English word bugge is the basis for the terms "bugbear" and "bugaboo" as terms used for a monster.[4] Baffle Ball, the first mechanical pinball game, was advertised as being "free of bugs" in 1931.[5] Problems with military gear during World War II were referred to as bugs (or glitches).[6] In a book published in 1942, Louise Dickinson Rich, speaking of a powered ice cutting machine, said, "Ice sawing was suspended until the creator could be brought in to take the bugs out of his darling."[7]
Isaac Asimov used the term "bug" to relate to issues with a robot in his short story "Catch That Rabbit", published in 1944, and included in his well-known collection of short stories I, Robot. From page 1 of "Catch That Rabbit": "U.S. Robots had to get the bugs out of the multiple robot, and there were plenty of bugs, and there are always at least half a dozen bugs left for the field-testing."
A page from the Harvard Mark II electromechanical computer's log, featuring a dead moth that was removed from the device
The term "bug" was used in an account by computer pioneer Grace Hopper, who publicized the cause of a malfunction in an early electromechanical computer.[8] A typical version of the story is:
In 1946, when Hopper was released from active duty, she joined the Harvard Faculty at the Computation Laboratory where she continued her work on the Mark II and Mark III. Operators traced an error in the Mark II to a moth trapped in a relay, coining the term bug. This bug was carefully removed and taped to the log book. Stemming from the first bug, today we call errors or glitches in a program a bug.[9]
Hopper did not find the bug, as she readily acknowledged. The date in the log book was September 9, 1947.[10][11][12] The operators who found it, including William "Bill" Burke, later of the Naval Weapons Laboratory, Dahlgren, Virginia,[13] were familiar with the engineering term and amusedly kept the insect with the notation "First actual case of bug being found." Hopper loved to recount the story.[14] This log book, complete with attached moth, is part of the collection of the Smithsonian National Museum of American History.[11]
The related term "debug" also appears to predate its usage in computing: the Oxford English Dictionary's etymology of the word contains an attestation from 1945, in the context of aircraft engines.[15]
History[edit]
The concept that software might contain errors dates back to Ada Lovelace's 1843 notes on the analytical engine, in which she speaks of the possibility of program "cards" for Charles Babbage's analytical engine being erroneous:
... an analysing process must equally have been performed in order to furnish the Analytical Engine with the necessary operative data; and that herein may also lie a possible source of error. Granted that the actual mechanism is unerring in its processes, the cards may give it wrong orders.
"Bugs in the System" report[edit]
The Open Technology Institute, run by the group, New America,[16] released a report "Bugs in the System" in August 2016 stating that U.S. policymakers should make reforms to help researchers identify and address software bugs. The report "highlights the need for reform in the field of software vulnerability discovery and disclosure."[17] One of the report’s authors said that Congress has not done enough to address cyber software vulnerability, even though Congress has passed a number of bills to combat the larger issue of cyber security.[17]
Government researchers, companies, and cyber security experts are the people who typically discover software flaws. The report calls for reforming computer crime and copyright laws.[17]
"The Computer Fraud and Abuse Act, the Digital Millennium Copyright Act and the Electronic Communications Privacy Act criminalize and create civil penalties for actions that security researchers routinely engage in while conducting legitimate security research, the report said."[17]
Terminology[edit]
There is ongoing debate over the use of the term "bug" to describe software errors. One argument is that the word "bug" is divorced from a sense that a human being caused the problem, and instead implies that the defect arose on its own, leading to a push to abandon the term "bug" in favor of terms such as "defect", with limited success.[18] Since the 1970s Gary Kildall somewhat humorously suggested to use the term "blunder".[19][20]
In software engineering, mistake metamorphism (from Greek meta = "change", morph = "form") refers to the evolution of a defect in the final stage of software deployment. Transformation of a "mistake" committed by an analyst in the early stages of the software development lifecycle, which leads to a "defect" in the final stage of the cycle has been called 'mistake metamorphism'.[21]
Different stages of a "mistake" in the entire cycle may be described as "mistakes", "anomalies", "faults", "failures", "errors", "exceptions", "crashes", "bugs", "defects", "incidents", or "side effects".[21]
Prevention[edit]
The software industry has put much effort into reducing bug counts.[22][23] These include:
Typographical errors[edit]
Bugs usually appear when the programmer makes a logic error. Various innovations in programming style and defensive programming are designed to make these bugs less likely, or easier to spot. Some typos, especially of symbols or logical/mathematical operators, allow the program to operate incorrectly, while others such as a missing symbol or misspelled name may prevent the program from operating. Compiled languages can reveal some typos when the source code is compiled.
Development methodologies[edit]
Several schemes assist managing programmer activity so that fewer bugs are produced. Software engineering (which addresses software design issues as well) applies many techniques to prevent defects. For example, formal program specifications state the exact behavior of programs so that design bugs may be eliminated. Unfortunately, formal specifications are impractical for anything but the shortest programs, because of problems of combinatorial explosion and indeterminacy.
Unit testing involves writing a test for every function (unit) that a program is to perform.
In test-driven development unit tests are written before the code and the code is not considered complete until all tests complete successfully.
Agile software development involves frequent software releases with relatively small changes. Defects are revealed by user feedback.
Open source development allows anyone to examine source code. A school of thought popularized by Eric S. Raymond as Linus's Law says that popular open-source software has more chance of having few or no bugs than other software, because "given enough eyeballs, all bugs are shallow".[24] This assertion has been disputed, however: computer security specialist Elias Levy wrote that "it is easy to hide vulnerabilities in complex, little understood and undocumented source code," because, "even if people are reviewing the code, that doesn't mean they're qualified to do so."[25] An example of this actually happening, accidentally, was the 2008 OpenSSL vulnerability in Debian.
Programming language support[edit]
Programming languages include features to help prevent bugs, such as static type systems, restricted namespaces and modular programming. For example, when a programmer writes (pseudocode) LET REAL_VALUE PI = "THREE AND A BIT", although this may be syntactically correct, the code fails a type check. Compiled languages catch this without having to run the program. Interpreted languages catch such errors at runtime. Some languages deliberate exclude features that easily lead to bugs, at the expense of slower performance: the general principle being that, it is almost always better to write simpler, slower code than inscrutable code that runs slightly faster, especially considering that maintenance cost is substantial. For example, the Java programming language does not support pointer arithmetic; implementations of some languages such as Pascal and scripting languages often have runtime bounds checking of arrays, at least in a debugging build.
Code analysis[edit]
Tools for code analysis help developers by inspecting the program text beyond the compiler's capabilities to spot potential problems. Although in general the problem of finding all programming errors given a specification is not solvable (see halting problem), these tools exploit the fact that human programmers tend to make certain kinds of simple mistakes often when writing software.
Instrumentation[edit]
Tools to monitor the performance of the software as it is running, either specifically to find problems such as bottlenecks or to give assurance as to correct working, may be embedded in the code explicitly (perhaps as simple as a statement saying PRINT "I AM HERE"), or provided as tools. It is often a surprise to find where most of the time is taken by a piece of code, and this removal of assumptions might cause the code to be rewritten.
Testing[edit]
Software testers are people whose primary task is to find bugs, or write code to support testing. On some projects, more resources may be spent on testing than in developing the program.
Measurements during testing can provide an estimate of the number of likely bugs remaining; this becomes more reliable the longer a product is tested and developed.[citation needed]
Debugging[edit]
The typical bug history (GNU Classpath project data). A new bug submitted by the user is unconfirmed. Once it has been reproduced by a developer, it is a confirmed bug. The confirmed bugs are later fixed. Bugs belonging to other categories (unreproducible, will not be fixed, etc.) are usually in the minority
Main article: Debugging
Finding and fixing bugs, or debugging, is a major part of computer programming. Maurice Wilkes, an early computing pioneer, described his realization in the late 1940s that much of the rest of his life would be spent finding mistakes in his own programs.[26]
Usually, the most difficult part of debugging is finding the bug. Once it is found, correcting it is usually relatively easy. Programs known as debuggers help programmers locate bugs by executing code line by line, watching variable values, and other features to observe program behavior. Without a debugger, code may be added so that messages or values may be written to a console or to a window or log file to trace program execution or show values.
However, even with the aid of a debugger, locating bugs is something of an art. It is not uncommon for a bug in one section of a program to cause failures in a completely different section,(For example in Java 8,the debugger won't point out those exceptions in which line the bug inside stream function is located but will point out the line where stream API itself located.[27] Or an error in a graphics rendering routine causing a file I/O routine to fail) thus making it especially difficult to track, in an apparently unrelated part of the system.
Sometimes, a bug is not an isolated flaw, but represents an error of thinking or planning on the part of the programmer. Such logic errors require a section of the program to be overhauled or rewritten. As a part of code review, stepping through the code and imagining or transcribing the execution process may often find errors without ever reproducing the bug as such.
More typically, the first step in locating a bug is to reproduce it reliably. Once the bug is reproducible, the programmer may use a debugger or other tool while reproducing the error to find the point at which the program went astray.
Some bugs are revealed by inputs that may be difficult for the programmer to re-create. One cause of the Therac-25 radiation machine deaths was a bug (specifically, a race condition) that occurred only when the machine operator very rapidly entered a treatment plan; it took days of practice to become able to do this, so the bug did not manifest in testing or when the manufacturer attempted to duplicate it. Other bugs may disappear when the program is run with a debugger; these heisenbugs (humorously named after the Heisenberg uncertainty principle).
Since the 1990s, particularly following the Ariane 5 Flight 501 disaster, interest in automated aids to debugging rose, such as static code analysis by abstract interpretation.[citation needed]
Some classes of bugs have nothing to do with the code. Faulty documentation or hardware may lead to problems in system use, even though the code matches the documentation. In some cases, changes to the code eliminate the problem even though the code then no longer matches the documentation. Embedded systems frequently work around hardware bugs, since to make a new version of a ROM is much cheaper than remanufacturing the hardware, especially if they are commodity items.
Bug management[edit]
Bug management includes the process of documenting, categorizing, assigning, reproducing, correcting and releasing the corrected code. Proposed changes to software – bugs as well as enhancement requests and even entire releases – are commonly tracked and managed using bug tracking systems or issue tracking systems. The items added may be called defects, tickets, issues, or, following the agile development paradigm, stories and epics. Categories may be objective, subjective or a combination, such as version number, area of the software, severity and priority, as well as what type of issue it is, such as a feature request or a bug.
Severity[edit]
Severity is the impact the bug has on system operation. This impact may be data loss, financial, loss of goodwill and wasted effort. Severity levels are not standardized. Impacts differ across industry. A crash in a video game has a totally different impact than a crash in a web browser, or real time monitoring system. For example, bug severity levels might be "crash or hang", "no workaround" (meaning there is no way the customer can accomplish a given task), "has workaround" (meaning the user can still accomplish the task), "visual defect" (for example, a missing image or displaced button or form element), or "documentation error". Some software publishers use more qualified severities such as "critical", "high", "low", "blocker" or "trivial".[28] The severity of a bug may be a separate category to its priority for fixing, and the two may be quantified and managed separately.
Priority[edit]
Priority controls where a bug falls on the list of planned changes. The priority is decided by each software producer. Priorities are sometimes numerical and sometimes named, such as "critical," "high," "low" or "deferred"; note that these may be similar or even identical to severity ratings when looking at different software producers. For example, priority 1 bugs may always be fixed for the next release, while "5" bugs may never be fixed. Industry practice employs an inverted scale, so that highest priority are low numbers (0 and 1), while larger numbers indicate lower priority.
Software releases[edit]
It is common practice to release software with known, low-priority bugs. Most big software projects maintain two lists of "known bugs" – those known to the software team, and those to be told to users.[citation needed] The second list informs users about bugs that are not fixed in a specific release and workarounds may be offered. Releases are of different kinds. Bugs of sufficiently high priority may warrant a special release of part of the code containing only modules with those fixes. These are known as patches. Most releases include a mixture of behavior changes and multiple bug fixes. Releases that emphasize bug fixes are known as maintenance releases. Releases that emphasize feature additions/changes are known as major releases and often have names to distinguish the new features from the old.
Reasons that a software publisher opts not to patch or even fix a particular bug include:
A deadline must be met and resources are insufficient to fix all bugs by the deadline.[29]
The bug is already fixed in an upcoming release, and it is not of high priority.
The changes required to fix the bug are too costly or affect too many other components, requiring a major testing activity.
It may be suspected, or known, that some users are relying on the existing buggy behavior; a proposed fix may introduce a breaking change.
The problem is in an area that will be obsolete with an upcoming release; fixing it is unnecessary.
It's "not a bug". A misunderstanding has arisen between expected and perceived behavior, when such misunderstanding is not due to confusion arising from design flaws, or faulty documentation.
Types[edit]
This section contains embedded lists that may be poorly defined, unverified or indiscriminate. Please help to clean it up to meet Wikipedia's quality standards. Where appropriate, incorporate items into the main body of the article. (August 2015)
This section is in a list format that may be better presented using prose. You can help by converting this section to prose, if appropriate. Editing help is available. (August 2015)
In software development projects, a "mistake" or "fault" may be introduced at any stage. Bugs arise from oversights or misunderstandings made by a software team during specification, design, coding, data entry or documentation. For example, a relatively simple program to alphabetize a list of words, the design might fail to consider what should happen when a word contains a hyphen. Or when converting an abstract design into code, the coder might inadvertently create an off-by-one error and fail to sort the last word in a list. Errors may be as simple as a typing error: a "<" where a ">" was intended.
Another category of bug is called a race condition that may occur when programs have multiple components executing at the same time. If the components interact in a different order than the developer intended, they could interfere with each other and stop the program from completing its tasks. These bugs may be difficult to detect or anticipate, since they may not occur during every execution of a program.
Conceptual errors are a developer's misunderstanding of what the software must do. The resulting software may perform according to the developer's understanding, but not what is really needed. Other types:
Arithmetic[edit]
Division by zero.
Arithmetic overflow or underflow.
Loss of arithmetic precision due to rounding or numerically unstable algorithms.
Logic[edit]
Infinite loops and infinite recursion.
Off-by-one error, counting one too many or too few when looping.
Syntax[edit]
Use of the wrong operator, such as performing assignment instead of equality test. For example, in some languages x=5 will set the value of x to 5 while x==5 will check whether x is currently 5 or some other number. Interpreted languages allow such code to fail. Compiled languages can catch such errors before testing begins.
Resource[edit]
Null pointer dereference.
Using an uninitialized variable.
Using an otherwise valid instruction on the wrong data type (see packed decimal/binary coded decimal).
Access violations.
Resource leaks, where a finite system resource (such as memory or file handles) become exhausted by repeated allocation without release.
Buffer overflow, in which a program tries to store data past the end of allocated storage. This may or may not lead to an access violation or storage violation. These are known as security bugs.
Excessive recursion which—though logically valid—causes stack overflow.
Use-after-free error, where a pointer is used after the system has freed the memory it references.
Double free error.
Multi-threading[edit]
Deadlock, where task A can't continue until task B finishes, but at the same time, task B can't continue until task A finishes.
Race condition, where the computer does not perform tasks in the order the programmer intended.
Concurrency errors in critical sections, mutual exclusions and other features of concurrent processing. Time-of-check-to-time-of-use (TOCTOU) is a form of unprotected critical section.
Interfacing[edit]
Incorrect API usage.
Incorrect protocol implementation.
Incorrect hardware handling.
Incorrect assumptions of a particular platform.
Incompatible systems. A new API or communications protocol may seem to work when two systems use different versions, but errors may occur when a function or feature implemented in one version is changed or missing in another. In production systems which must run continually, shutting down the entire system for a major update may not be possible, such as in the telecommunication industry[30] or the internet.[31][32][33] In this case, smaller segments of a large system are upgraded individually, to minimize disruption to a large network. However, some sections could be overlooked and not upgraded, and cause compatibility errors which may be difficult to find and repair.
Teamworking[edit]
Unpropagated updates; e.g. programmer changes "myAdd" but forgets to change "mySubtract", which uses the same algorithm. These errors are mitigated by the Don't Repeat Yourself philosophy.
Comments out of date or incorrect: many programmers assume the comments accurately describe the code.
Differences between documentation and product.
Implications[edit]
The amount and type of damage a software bug may cause naturally affects decision-making, processes and policy regarding software quality. In applications such as manned space travel or automotive safety, since software flaws have the potential to cause human injury or even death, such software will have far more scrutiny and quality control than, for example, an online shopping website. In applications such as banking, where software flaws have the potential to cause serious financial damage to a bank or its customers, quality control is also more important than, say, a photo editing application. NASA's Software Assurance Technology Center managed to reduce the number of errors to fewer than 0.1 per 1000 lines of code (SLOC)[citation needed] but this was not felt to be feasible for projects in the business world.
Well-known bugs[edit]
Main article: List of software bugs
A number of software bugs have become well-known, usually due to their severity: examples include various space and military aircraft crashes. Possibly the most famous bug is the Year 2000 problem, also known as the Y2K bug, in which it was feared that worldwide economic collapse would happen at the start of the year 2000 as a result of computers thinking it was 1900. (In the end, no major problems occurred.)
The 2012 stock trading disruption involved one such incompatibility between the old API and a new API.
In popular culture[edit]
In Robert A. Heinlein's 1966 novel The Moon Is a Harsh Mistress, computer technician Manuel Davis blames a real bug for a (non-existent) failure of supercomputer Mike, presenting a dead fly as evidence.
In the 1968 novel 2001: A Space Odyssey (and its corresponding 1968 film adaptation), a spaceship's onboard computer, HAL 9000, attempts to kill all its crew members. In the follow-up 1982 novel, 2010: Odyssey Two, and the accompanying 1984 film, 2010, it is revealed that this action was caused by the computer having been programmed with two conflicting objectives: to fully disclose all its information, and to keep the true purpose of the flight secret from the crew; this conflict caused HAL to become paranoid and eventually homicidal.
In the 1999 American comedy Office Space, the plot focuses on an attempt by three employees to exploit the company's preoccupation with fixing the Y2K computer bug by infecting the company's computer system with a virus that sends rounded off pennies to a separate bank account. The plan backfires as the virus itself has its own bug which sends large amounts of money to the account prematurely.
In 2000, Joe Trela correctly answered moth for the million dollar question: "What insect shorted out an early supercomputer and inspired the term Computer Bug." in the United States version of the game show Who Wants to be a Millionaire.
The 2004 novel The Bug, by Ellen Ullman, is about a programmer's attempt to find an elusive bug in a database application.[34]
The 2008 Canadian film Control Alt Delete is about a computer programmer at the end of 1999 struggling to fix bugs at his company related to the year 2000 problem.
See also[edit]
Software Testing portal
Anti-pattern
Bug bounty program
Glitch removal
ISO/IEC 9126, which classifies a bug as either a defect or a nonconformity
Orthogonal Defect Classification
Racetrack problem
RISKS Digest
Software defect indicator
Software regression
Software rot
References[edit]
Jump up ^ Prof. Simon Rogerson. "The Chinook Helicopter Disaster". Ccsr.cse.dmu.ac.uk. Archived from the original on July 17, 2012. Retrieved September 24, 2012.
Jump up ^ "Software bugs cost US economy dear". Web.archive.org. June 10, 2009. Archived from the original on June 10, 2009. Retrieved September 24, 2012. CS1 maint: Unfit url (link)
Jump up ^ Edison to Puskas, 13 November 1878, Edison papers, Edison National Laboratory, U.S. National Park Service, West Orange, N.J., cited in Hughes, Thomas Parke (1989). American Genesis: A Century of Invention and Technological Enthusiasm, 1870-1970. Penguin Books. p. 75. ISBN 978-0-14-009741-2.
Jump up ^ Computerworld staff (September 3, 2011). "Moth in the machine: Debugging the origins of 'bug'". Computerworld. Archived from the original on August 25, 2015.
Jump up ^ "Baffle Ball". Internet Pinball Database. (See image of advertisement in reference entry)
Jump up ^ "Modern Aircraft Carriers are Result of 20 Years of Smart Experimentation". Life. June 29, 1942. p. 25. Archived from the original on June 4, 2013. Retrieved November 17, 2011.
Jump up ^ Dickinson Rich, Louise (1942), We Took to the Woods, JB Lippincott Co, p. 93, LCCN 42024308, OCLC 405243, archived from the original on March 16, 2017.
Jump up ^ FCAT NRT Test, Harcourt, March 18, 2008
Jump up ^ "Danis, Sharron Ann: "Rear Admiral Grace Murray Hopper"". ei.cs.vt.edu. February 16, 1997. Retrieved January 31, 2010.
Jump up ^ "Bug Archived March 23, 2017, at the Wayback Machine.", The Jargon File, ver. 4.4.7. Retrieved June 3, 2010.
^ Jump up to: a b "Log Book With Computer Bug Archived March 23, 2017, at the Wayback Machine.", National Museum of American History, Smithsonian Institution.
Jump up ^ "The First "Computer Bug", Naval Historical Center. But note the Harvard Mark II computer was not complete until the summer of 1947.
Jump up ^ IEEE Annals of the History of Computing, Vol 22 Issue 1, 2000
Jump up ^ James S. Huggins. "First Computer Bug". Jamesshuggins.com. Archived from the original on August 16, 2000. Retrieved September 24, 2012.
Jump up ^ Journal of the Royal Aeronautical Society. 49, 183/2, 1945 "It ranged ... through the stage of type test and flight test and 'debugging' ..."
Jump up ^ Wilson, Andi; Schulman, Ross; Bankston, Kevin; Herr, Trey. "Bugs in the System" (PDF). Open Policy Institute. Archived (PDF) from the original on September 21, 2016. Retrieved August 22, 2016.
^ Jump up to: a b c d Rozens, Tracy (2016-08-12). "Cyber reforms needed to strengthen software bug discovery and disclosure: New America report – Homeland Preparedness News". Retrieved 2016-08-23.
Jump up ^ "News at SEI 1999 Archive". cmu.edu. Archived from the original on May 26, 2013.
Jump up ^ Shustek, Len (August 2, 2016). "In His Own Words: Gary Kildall". Remarkable People. Computer History Museum. Archived from the original on December 17, 2016.
Jump up ^ Kildall, Gary Arlen (August 2, 2016) [1993]. Kildall, Scott; Kildall, Kristin, eds. "Computer Connections: People, Places, and Events in the Evolution of the Personal Computer Industry" (Manuscript, part 1). Kildall Family: 14–15. Archived from the original on November 17, 2016. Retrieved November 17, 2016.
^ Jump up to: a b "Testing experience : te : the magazine for professional testers". Testing Experience. Germany: testingexperience: 42. March 2012. ISSN 1866-5705. (subscription required)
Jump up ^ Huizinga, Dorota; Kolawa, Adam (2007). Automated Defect Prevention: Best Practices in Software Management. Wiley-IEEE Computer Society Press. p. 426. ISBN 0-470-04212-5. Archived from the original on April 25, 2012.
Jump up ^ McDonald, Marc; Musson, Robert; Smith, Ross (2007). The Practical Guide to Defect Prevention. Microsoft Press. p. 480. ISBN 0-7356-2253-1. Archived from the original on December 2, 2006.
Jump up ^ "Release Early, Release Often" Archived May 14, 2011, at the Wayback Machine., Eric S. Raymond, The Cathedral and the Bazaar
Jump up ^ "Wide Open Source" Archived September 29, 2007, at the Wayback Machine., Elias Levy, SecurityFocus, April 17, 2000
Jump up ^ Maurice Wilkes Quotes
Jump up ^ https://blog.jooq.org/2015/12/08/3-reasons-why-you-shouldnt-replace-your-for-loops-by-stream-foreach/
Jump up ^ "5.3. Anatomy of a Bug". bugzilla.org. Archived from the original on May 23, 2013.
Jump up ^ "The Next Generation 1996 Lexicon A to Z: Slipstream Release". Next Generation. No. 15. Imagine Media. March 1996. p. 41.
Jump up ^ Kimbler, K. (1998). Feature Interactions in Telecommunications and Software Systems V. IOS Press. p. 8. ISBN 978-90-5199-431-5.
Jump up ^ Syed,, Mahbubur Rahman (1 July 2001). Multimedia Networking: Technology, Management and Applications: Technology, Management and Applications. Idea Group Inc (IGI). p. 398. ISBN 978-1-59140-005-9.
Jump up ^ Wu, Chwan-Hwa (John); Irwin, J. David (19 April 2016). Introduction to Computer Networks and Cybersecurity. CRC Press. p. 500. ISBN 978-1-4665-7214-0.
Jump up ^ RFC 1263: "TCP Extensions Considered Harmful" quote: "the time to distribute the new version of the protocol to all hosts can be quite long (forever in fact). ... If there is the slightest incompatibly between old and new versions, chaos can result."
Jump up ^ Ullman, Ellen (2004). The Bug. Picador. ISBN 1-250-00249-4.
Further reading[edit]
Allen, Mitch (May–June 2002). "Bug Tracking Basics: A beginner's guide to reporting and tracking defects". Software Testing & Quality Engineering Magazine. Vol. 4 no. 3. pp. 20–24. Retrieved December 19, 2017. CS1 maint: Date format (link)
External links[edit]
MediaWiki has documentation related to: Bug management
"Common Weakness Enumeration" – an expert webpage focus on bugs, at NIST.gov
BUG type of Jim Gray – another Bug type
Picture of the "first computer bug" at the Wayback Machine (archived January 12, 2015)
"The First Computer Bug!" – an email from 1981 about Adm. Hopper's bug
"Toward Understanding Compiler Bugs in GCC and LLVM". A 2016 study of bugs in compilers
Retrieved from "https://en.wikipedia.org/w/index.php?title=Software_bug&oldid=825240859"
Categories:
Software bugs
Hidden categories:
CS1 maint: Unfit url
Webarchive template wayback links
Pages containing links to subscription-only content
Pages using RFC magic links
Articles needing additional references from September 2017
All articles needing additional references
Use mdy dates from September 2012
All articles with unsourced statements
Articles with unsourced statements from February 2017
Articles with unsourced statements from July 2013
Articles needing cleanup from August 2015
All pages needing cleanup
Wikipedia list cleanup from August 2015
Articles with sections that need to be turned into prose from August 2015
Articles with unsourced statements from September 2009
CS1 maint: Date format
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Namespaces
Article
Talk
Variants
Views
Read
Edit
View history
More
Search
Navigation
Main page
Contents
Featured content
Current events
Random article
Donate to Wikipedia
Wikipedia store
Interaction
Help
About Wikipedia
Community portal
Recent changes
Contact page
Tools
What links here
Related changes
Upload file
Special pages
Permanent link
Page information
Wikidata item
Cite this page
Print/export
Create a book
Download as PDF
Printable version
In other projects
Wikimedia Commons
Languages
العربية
বাংলা
Български
Català
Čeština
Dansk
Deutsch
Ελληνικά
Español
Esperanto
Euskara
فارسی
Français
Frysk
Gaeilge
Galego
한국어
हिन्दी
Hrvatski
Bahasa Indonesia
Italiano
עברית
Lëtzebuergesch
Lumbaart
Magyar
മലയാളം
Bahasa Melayu
Nederlands
日本語
Norsk
Occitan
Polski
Português
Русский
Scots
Shqip
Simple English
Slovenščina
Српски / srpski
Suomi
Svenska
தமிழ்
తెలుగు
ไทย
Türkçe
Українська
吴语
ייִדיש
粵語
中文
Edit links
This page was last edited on 12 February 2018, at 07:26.
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.
Privacy policy
About Wikipedia
Disclaimers
Contact Wikipedia
Developers
Cookie statement
Mobile view
Enable previews

values: mw-page-base noprint

values: mw-head-base noprint

values: firstHeading firstHeading en

values: siteSub noprint

values: jump-to-nav mw-jump

values:
/wiki/Wikipedia:Bug_reports
mw-redirect
Wikipedia:Bug reports

value: span

attrs: role class

values:
note
hatnote navigation-not-searchable

value: img

attrs: alt src width height srcset data-file-width data-file-height

attrs: href class

value: td

value: b

attrs: class href

values: Help:Introduction to referencing with Wiki Markup/1

value: small

values: plainlinks metadata ambox ambox-content ambox-Refimprove

values:
/wiki/Software_development_methodology
mw-redirect
Software development methodology

values:
/wiki/Model-driven_development
mw-redirect
Model-driven development

values:
/wiki/Scaled_Agile_Framework
mw-redirect
Scaled Agile Framework

values:
/wiki/Continuous_Integration
mw-redirect
Continuous Integration

values:
/wiki/Continuous_Delivery
mw-redirect
Continuous Delivery

values:
/wiki/Pair_Programming
mw-redirect
Pair Programming

values: Template talk:Software development process

values: float:right;clear:right;width:22.0em;margin:0 0 1.0em 1.0em;background:#f9f9f9;border:1px solid #aaa;padding:0.2em;border-spacing:0.4em 0;text-align:center;line-height:1.4em;font-size:88%

values:
/wiki/Freeze_(computing)
mw-redirect
Freeze (computing)

values:
/wiki/Security_bugs
mw-redirect
Security bugs

values:
/wiki/Black_hat_hacking
mw-redirect
Black hat hacking

values:
/wiki/Ariane_5_Flight_501
mw-redirect
Ariane 5 Flight 501

values:
/wiki/CH-47_Chinook
mw-redirect
CH-47 Chinook

values:
/wiki/Department_of_Commerce
mw-redirect
Department of Commerce

values: National Institute of Standards and Technology

attrs: alt src width height class srcset data-file-width data-file-height

values: Naval Surface Warfare Center Dahlgren Division

values: Ada Byron's notes on the analytical engine

values:
/wiki/Analytical_engine
mw-redirect
Analytical engine

values: Edit section: "Bugs in the System" report

values:
/wiki/Program_specification
mw-redirect
Program specification

values: Edit section: Programming language support

values:
/wiki/Type_checking
mw-redirect
Type checking

values:
/wiki/Maintenance_cost
mw-redirect
Maintenance cost

values:
/wiki/Static_code_analysis
mw-redirect
Static code analysis

values:
/wiki/Software_tester
mw-redirect
Software tester

values: This claim needs references to reliable sources. (February 2017)

values:
noprint Inline-Template Template-Fact
white-space:nowrap;

values:
/wiki/Commodity_items
mw-redirect
Commodity items

values:
/wiki/Agile_development
mw-redirect
Agile development

values:
/wiki/Version_number
mw-redirect
Version number

values: This claim needs references to reliable sources. (July 2013)

values: Wikipedia:Manual of Style/Embedded lists

values:
plainlinks metadata ambox ambox-style
presentation

values:
/wiki/Wikipedia:Embedded_list
mw-redirect
Wikipedia:Embedded list

values: plainlinks metadata ambox ambox-style ambox-Prose

values:
/wiki/Arithmetic_overflow
mw-redirect
Arithmetic overflow

values:
/wiki/Arithmetic_precision
mw-redirect
Arithmetic precision

values:
/wiki/Packed_decimal
mw-redirect
Packed decimal

values:
/wiki/Binary_coded_decimal
mw-redirect
Binary coded decimal

values:
/wiki/Access_violation
mw-redirect
Access violation

values:
/wiki/Communications_protocol
mw-redirect
Communications protocol

values:
/wiki/Automotive_safety
mw-redirect
Automotive safety

values: This claim needs references to reliable sources. (September 2009)

values:
/wiki/Who_Wants_to_be_a_Millionaire
mw-redirect
Who Wants to be a Millionaire

values:
/wiki/Portal:Software_Testing
mw-redirect
Portal:Software Testing

values: display:table-cell;padding:0.2em 0.2em 0.2em 0.3em;vertical-align:middle

values: margin:0.5em 0 0.5em 1em;border:solid #aaa 1px

values:
nofollow
external text
http://www.ipdb.org/machine.cgi?gid=129

values:
nofollow
external text
//lccn.loc.gov/42024308

values:
nofollow
external text
//www.worldcat.org/oclc/405243

values:
nofollow
external text
http://catb.org/jargon/html/B/bug.html

values:
nofollow
external text
//www.worldcat.org/issn/1866-5705

values:
nofollow
external text
http://www.securityfocus.com/news/19

values:
/wiki/Imagine_Media
mw-redirect
Imagine Media

values:
external mw-magiclink-rfc
nofollow
https://tools.ietf.org/html/rfc1263

values:
nofollow
external text
https://nvd.nist.gov/cwe.cfm

values: Category:Webarchive template wayback links

values: Category:Pages containing links to subscription-only content

values: Category:Articles needing additional references from September 2017

values: Category:All articles needing additional references

values: Category:Use mdy dates from September 2012

values: Category:All articles with unsourced statements

values: Category:Articles with unsourced statements from February 2017

values: Category:Articles with unsourced statements from July 2013

values: Category:Articles needing cleanup from August 2015

values: Category:Wikipedia list cleanup from August 2015

values: Category:Articles with sections that need to be turned into prose from August 2015

values: Category:Articles with unsourced statements from September 2009

values: Discussion about edits from this IP address [ctrl-alt-n]

values: A list of edits made from this IP address [ctrl-alt-y]

values: You are encouraged to create an account and log in; however, it is not mandatory

values: You're encouraged to log in; however, it's not mandatory. [ctrl-alt-o]

values:
/wiki/Software_bug
View the content page [ctrl-alt-c]
c

values: Discussion about the content page [ctrl-alt-t]

values: p-namespaces navigation vectorTabs p-namespaces-label

values:
p-variants
navigation
vectorMenu emptyPortlet
p-variants-label

values: Past revisions of this page [ctrl-alt-h]

values: p-views navigation vectorTabs p-views-label

values:
p-cactions
navigation
vectorMenu emptyPortlet
p-cactions-label

values:
mw-wiki-logo
/wiki/Main_Page
Visit the main page

values:
/wiki/Main_Page
Visit the main page [ctrl-alt-z]
z

values: Featured content – the best of Wikipedia

values: portal navigation p-wikibase-otherprojects p-wikibase-otherprojects-label

values: خطأ برمجي – Arabic

values: সফটওয়্যার বাগ – Bangla

values: Програмна грешка – Bulgarian

values: اشکال نرم‌افزاری – Persian

values:
https://fy.wikipedia.org/wiki/Brek
Brek – Western Frisian
fy
fy
interlanguage-link-target

values:
https://gl.wikipedia.org/wiki/Bug
Bug – Galician
gl
gl
interlanguage-link-target

values: 소프트웨어 버그 – Korean

values: सॉफ्टवेयर बग – Hindi

values:
https://id.wikipedia.org/wiki/Kekutu
Kekutu – Indonesian
id
id
interlanguage-link-target

values:
https://it.wikipedia.org/wiki/Bug
Bug – Italian
it
it
interlanguage-link-target

values:
https://lb.wikipedia.org/wiki/Bug
Bug – Luxembourgish
lb
lb
interlanguage-link-target

values:
https://lmo.wikipedia.org/wiki/Bug
Bug – Lombard
lmo
lmo
interlanguage-link-target

values: സോഫ്റ്റ്‌വെയർ ബഗ്ഗ് – Malayalam

values:
https://ms.wikipedia.org/wiki/Pepijat
Pepijat – Malay
ms
ms
interlanguage-link-target

values:
https://pt.wikipedia.org/wiki/Bug
Bug – Portuguese
pt
pt
interlanguage-link-target

values: Программная ошибка – Russian

values:
https://sq.wikipedia.org/wiki/Bug
Bug – Albanian
sq
sq
interlanguage-link-target

values: Баг (информатика) – Serbian

values: மென்பொருள் வழு – Tamil

values: సాఫ్ట్‌వేర్ దోషం – Telugu

values: סאפטוועיר באג – Yiddish

values:
https://zh-yue.wikipedia.org/wiki/Bug
Bug – Cantonese
zh-yue
zh-yue
interlanguage-link-target

values: /static/images/wikimedia-button-1.5x.png 1.5x, /static/images/wikimedia-button-2x.png 2x

values: /static/images/poweredby_mediawiki_132x47.png 1.5x, /static/images/poweredby_mediawiki_176x62.png 2x

values:
suggestions
display: none; font-size: 13px;

values: mediawiki ltr sitedir-ltr mw-hide-empty-elt ns-0 ns-subject page-Software_bug rootpage-Software_bug skin-vector action-view