Debugging – S3lab http://s3lab.deusto.es S3lab Security Blog Wed, 06 May 2020 12:51:35 +0000 en-US hourly 1 https://wordpress.org/?v=5.1.5 Starting code debugging (II) – Breakpoints http://s3lab.deusto.es/starting-code-debugging-2/ Fri, 16 Mar 2018 10:57:02 +0000 http://s3lab.deusto.es/?p=9697 One of the most useful functions provided by debuggers is setting breakpoints in certain lines of code to stop execution at those points and examine the status of the program. Breakpoints can be both hardware and software. GDB can set…

Read more ›

The post Starting code debugging (II) – Breakpoints appeared first on S3lab.

]]> One of the most useful functions provided by debuggers is setting breakpoints in certain lines of code to stop execution at those points and examine the status of the program. Breakpoints can be both hardware and software. GDB can set hardware breakpoints in three different ways:

The post Starting code debugging (II) – Breakpoints appeared first on S3lab.

]]> Starting code debugging (I) http://s3lab.deusto.es/starting-code-debugging-1/ Wed, 31 Jan 2018 16:23:30 +0000 http://s3lab.deusto.es/?p=9674 Errors are a collateral (and undesired) phenomenon that occur when writing code. Some, like syntactic errors, are easy to detect and correct, since normally the compiler,  interpreter or  IDE itself will warn us that we have some open parentheses for…

Read more ›

The post Starting code debugging (I) appeared first on S3lab.

]]> Errors are a collateral (and undesired) phenomenon that occur when writing code. Some, like syntactic errors, are easy to detect and correct, since normally the compiler,  interpreter or  IDE itself will warn us that we have some open parentheses for example. However, other errors can produce intense headaches, such as a segmentation fault somewhere within miles of lines of code that is triggered by a series of specific conditions.

The post Starting code debugging (I) appeared first on S3lab.

]]>