AskIgor Image Gallery

	Image Gallery

Here are some images for presentations or publications about AskIgor. You are allowed to use these images free of charge, as long as you reference the source, www.askigor.org.

Debugging with AskIgor
(Fehlersuche mit AskIgor)

JPG, 4682x951 (for printing)
JPG, 750x153 (for screen viewing)
JPG, 4682x951 (German version; for printing)
JPG, 750x153 (German version; for screen viewing)
This diagram shows the debugging process with AskIgor from a user's perspective.

Debugging - the traditional way and the AskIgor way
(Fehlersuche - herkömmlich und mit AskIgor)

JPG, 4682x2389 (for printing)
JPG, 750x383 (for screen viewing)
JPG, 4682x2389 (German version; for printing)
JPG, 750x383 (German version; for screen viewing)
This diagram contrasts traditional (manual) debugging with the AskIgor process.

Submitting a program

JPG, 602x638
This picture shows the initial AskIgor screen in a Mozilla web browser. The user is preparing to upload the GNU C compiler (GCC).

How the failure came to be

JPG, 602x631
This picture shows the AskIgor diagnosis screen in a Mozilla web browser. The user sees how the failure came to be.

A program state

JPG, 1200x730
This picture shows the program state of the GNU C compiler (GCC): 70,000 variables are connected by references. One of these refers a bad value—and Igor finds out the one.

Behind the scenes

JPG, 942x576
PDF
Igor works by accessing and comparing program states of two runs—a working and a failing one. By systematic testing, Igor isolates the failure-inducing difference—for instance, the one bad reference between two variables.

Professor Zeller

JPG, 512x689 (for viewing)
JPG, 2048x2756 (for printing)
Andreas Zeller, professor of computer science at Saarland University, Germany, conceived AskIgor after spending too many nights on debugging.

Images of Igor

	Debugging with AskIgor (Fehlersuche mit AskIgor) JPG, 4682x951 (for printing) JPG, 750x153 (for screen viewing) JPG, 4682x951 (German version; for printing) JPG, 750x153 (German version; for screen viewing) This diagram shows the debugging process with AskIgor from a user's perspective.
	Debugging - the traditional way and the AskIgor way (Fehlersuche - herkömmlich und mit AskIgor) JPG, 4682x2389 (for printing) JPG, 750x383 (for screen viewing) JPG, 4682x2389 (German version; for printing) JPG, 750x383 (German version; for screen viewing) This diagram contrasts traditional (manual) debugging with the AskIgor process.
	Submitting a program JPG, 602x638 This picture shows the initial AskIgor screen in a Mozilla web browser. The user is preparing to upload the GNU C compiler (GCC).
	How the failure came to be JPG, 602x631 This picture shows the AskIgor diagnosis screen in a Mozilla web browser. The user sees how the failure came to be.
	A program state JPG, 1200x730 This picture shows the program state of the GNU C compiler (GCC): 70,000 variables are connected by references. One of these refers a bad value—and Igor finds out the one.
	Behind the scenes JPG, 942x576 PDF Igor works by accessing and comparing program states of two runs—a working and a failing one. By systematic testing, Igor isolates the failure-inducing difference—for instance, the one bad reference between two variables.
	Professor Zeller JPG, 512x689 (for viewing) JPG, 2048x2756 (for printing) Andreas Zeller, professor of computer science at Saarland University, Germany, conceived AskIgor after spending too many nights on debugging.