Wild Branch
Where a pointer is used as the address of the entry point to a program or start of a subroutine and is also either uninitialized or corrupted, if a call or jump is nevertheless made to this address, a "wild branch" is said to have occurred. The consequences are usually unpredictable and the error may present itself in several different ways depending upon whether or not the pointer is a "valid" address and whether or not there is (coincidentally) a valid instruction (opcode) at that address. The detection of a wild branch can present one of the most difficult and frustrating debugging exercises since much of the evidence may already have been destroyed beforehand or by execution of one or more inappropriate instructions at the branch location. If available, an instruction set simulator can usually not only detect a wild branch before it takes effect, but also provide a complete or partial trace of its history.
Read more about this topic: Pointer (computer Programming)
Famous quotes containing the words wild and/or branch:
“Men are all right for friends, but as soon as you marry them they turn into cranky old fathers, even the wild ones. They begin to tell you what’s sensible and what’s foolish, and want you to stick at home all the time. I prefer to be foolish when I feel like it, and be accountable to nobody.”
—Willa Cather (1873–1947)
“When I am finishing a picture I hold some God-made object up to it—a rock, a flower, the branch of a tree or my hand—as a kind of final test. If the painting stands up beside a thing man cannot make, the painting is authentic. If there’s a clash between the two, it is bad art.”
—Marc Chagall (1889–1985)