This document provides guidance and an overview to high level general features and updates for SUSE Linux Enterprise Server 12. Besides architecture or product-specific information, it also describes the capabilities and limitations of SLES 12. The VALGRINDDISCARDTRANSLATIONS client request is an alternative to −−smc−check=all and −−smc−check=all−non−file that requires more programmer effort but allows Valgrind to run your program faster, by telling it precisely when translations need to be re−made.

• Alternatives To Valgrind On Windows
• Alternative To Valgrind Mac
• Alternatives To Valgrind

22.1 Introduction

What do you do when R code throws an unexpected error? What tools do you have to find and fix the problem? This chapter will teach you the art and science of debugging, starting with a general strategy, then following up with specific tools.

I’ll show the tools provided by both R and the RStudio IDE. I recommend using RStudio’s tools if possible, but I’ll also show you the equivalents that work everywhere. You may also want to refer to the official RStudio debugging documentation which always reflects the latest version of RStudio.

NB: You shouldn’t need to use these tools when writing new functions. If you find yourself using them frequently with new code, reconsider your approach. Instead of trying to write one big function all at once, work interactively on small pieces. If you start small, you can quickly identify why something doesn’t work, and don’t need sophisticated debugging tools.

Outline

• Section 22.2 outlines a general strategy forfinding and fixing errors.

• Section 22.3 introduces you to the traceback() functionwhich helps you locate exactly where an error occurred.

• Section 22.4 shows you how to pause the execution of a functionand launch environment where you can interactively explore what’s happening.

• Section 22.5 discusses the challenging problemof debugging when you’re running code non-interactively.

• Section 22.6 discusses a handful of non-error problemsthat occassionally also need debugging.

22.2 Overall approach

Finding your bug is a process of confirming the many thingsthat you believe are true — until you find one which is nottrue.

—Norm Matloff

Finding the root cause of a problem is always challenging. Most bugs are subtle and hard to find because if they were obvious, you would’ve avoided them in the first place. A good strategy helps. Below I outline a four step process that I have found useful:

1. Google!

   Whenever you see an error message, start by googling it. If you’re lucky,you’ll discover that it’s a common error with a known solution. Whengoogling, improve your chances of a good match by removing any variablenames or values that are specific to your problem.

   You can automate this process with the erroristJames Balamuta, Errorist: Automatically Search Errors or Warnings, 2018, https://github.com/coatless/errorist.

   '>¹⁰⁷ and searcherJames Balamuta, Searcher: Query Search Interfaces, 2018, https://github.com/coatless/searcher.'>¹⁰⁸ packages. See their websites for more details.

2. Make it repeatable

   To find the root cause of an error, you’re going to need to execute thecode many times as you consider and reject hypotheses. To make thatiteration as quick possible, it’s worth some upfront investment to makethe problem both easy and fast to reproduce.

   Start by creating a reproducible example (Section 1.7).Next, make the example minimal by removing code and simplifying data.As you do this, you may discover inputs that don’t trigger the error.Make note of them: they will be helpful when diagnosing the root cause.

   If you’re using automated testing, this is also a good time to create anautomated test case. If your existing test coverage is low, take theopportunity to add some nearby tests to ensure that existing good behaviouris preserved. This reduces the chances of creating a new bug.

3. Figure out where it is

   If you’re lucky, one of the tools in the following section will help you toquickly identify the line of code that’s causing the bug. Usually, however,you’ll have to think a bit more about the problem. It’s a great idea toadopt the scientific method. Generate hypotheses, design experiments to testthem, and record your results. This may seem like a lot of work, but asystematic approach will end up saving you time. I often waste a lot of timerelying on my intuition to solve a bug (“oh, it must be an off-by-one error,so I’ll just subtract 1 here”), when I would have been better off taking asystematic approach.

   If this fails, you might need to ask help from someone else. If you’vefollowed the previous step, you’ll have a small example that’s easy toshare with others. That makes it much easier for other people to look atthe problem, and more likely to help you find a solution.

4. Fix it and test it

   Once you’ve found the bug, you need to figure out how to fix it and to checkthat the fix actually worked. Again, it’s very useful to have automatedtests in place. Not only does this help to ensure that you’ve actually fixedthe bug, it also helps to ensure you haven’t introduced any new bugs in theprocess. In the absence of automated tests, make sure to carefully recordthe correct output, and check against the inputs that previously failed.

22.3 Locating errors

Once you’ve made the error repeatable, the next step is to figure out where it comes from. The most important tool for this part of the process is traceback(), which shows you the sequence of calls (also known as the call stack, Section 7.5) that lead to the error.

Here’s a simple example: you can see that f() calls g() calls h() calls i(), which checks if its argument is numeric:

When we run f('a') code in RStudio we see:

Two options appear to the right of the error message: “Show Traceback” and “Rerun with Debug”. If you click “Show traceback” you see:

If you’re not using RStudio, you can use traceback() to get the same information (sans pretty formatting):

NB: You read the traceback() output from bottom to top: the initial call is f(), which calls g(), then h(), then i(), which triggers the error. If you’re calling code that you source()d into R, the traceback will also display the location of the function, in the form filename.r#linenumber. These are clickable in RStudio, and will take you to the corresponding line of code in the editor.

22.3.1 Lazy evaluation

One drawback to traceback() is that it always linearises the call tree, which can be confusing if there is much lazy evaluation involved (Section 7.5.2). For example, take the following example where the error happens when evaluating the first argument to f():

You can using rlang::with_abort() and rlang::last_trace() to see the call tree. Here, I think it makes it much easier to see the source of the problem. Look at the last branch of the call tree to see that the error comes from j() calling k().

NB: rlang::last_trace() is ordered in the opposite way to traceback(). We’ll come back to that issue in Section 22.4.2.4.

22.4 Interactive debugger

Sometimes, the precise location of the error is enough to let you track it down and fix it. Frequently, however, you need more information, and the easiest way to get it is with the interactive debugger which allows you to pause execution of a function and interactively explore its state.

If you’re using RStudio, the easiest way to enter the interactive debugger is through RStudio’s “Rerun with Debug” tool. This reruns the command that created the error, pausing execution where the error occurred. Otherwise, you can insert a call to browser() where you want to pause, and re-run the function. For example, we could insert a call browser() in g():

browser() is just a regular function call which means that you can run it conditionally by wrapping it in an if statement:

In either case, you’ll end up in an interactive environment inside the function where you can run arbitrary R code to explore the current state. You’ll know when you’re in the interactive debugger because you get a special prompt:

In RStudio, you’ll see the corresponding code in the editor (with the statement that will be run next highlighted), objects in the current environment in the Environment pane, and the call stack in the Traceback pane.

22.4.1browser() commands

As well as allowing you to run regular R code, browser() provides a few special commands. You can use them by either typing short text commands, or by clicking a button in the RStudio toolbar, Figure 22.1:

• Next, n: executes the next step in the function. If you have avariable named n, you’ll need print(n) to display its value.

• Step into, or s:works like next, but if the next step is a function, it will step into thatfunction so you can explore it interactively.

• Finish, or f:finishes execution of the current loop or function.

• Continue, c: leaves interactive debugging and continues regular executionof the function. This is useful if you’ve fixed the bad state and want tocheck that the function proceeds correctly.

• Stop, Q: stops debugging, terminates the function, and returns to the globalworkspace. Use this once you’ve figured out where the problem is, and you’reready to fix it and reload the code.

There are two other slightly less useful commands that aren’t available in the toolbar:

• Enter: repeats the previous command. I find this too easy to activateaccidentally, so I turn it off using options(browserNLdisabled = TRUE).

• where: prints stack trace of active calls (the interactive equivalent oftraceback).

22.4.2 Alternatives

There are three alternatives to using browser(): setting breakpoints in RStudio, options(error = recover), and debug() and other related functions.

22.4.2.1 Breakpoints

In RStudio, you can set a breakpoint by clicking to the left of the line number, or pressing Shift + F9. Breakpoints behave similarly to browser() but they are easier to set (one click instead of nine key presses), and you don’t run the risk of accidentally including a browser() statement in your source code. There are two small downsides to breakpoints:

• There are a few unusual situations in which breakpoints will not work.Read breakpoint troubleshooting for more details.

• RStudio currently does not support conditional breakpoints.

22.4.2.2recover()

Another way to activate browser() is to use options(error = recover). Now when you get an error, you’ll get an interactive prompt that displays the traceback and gives you the ability to interactively debug inside any of the frames:

You can return to default error handling with options(error = NULL).

22.4.2.3debug()

Another approach is to call a function that inserts the browser() call for you:

• debug() inserts a browser statement in the first line of the specifiedfunction. undebug() removes it. Alternatively, you can use debugonce()to browse only on the next run.

• utils::setBreakpoint() works similarly, but instead of taking a functionname, it takes a file name and line number and finds the appropriate functionfor you.

These two functions are both special cases of trace(), which inserts arbitrary code at any position in an existing function. trace() is occasionally useful when you’re debugging code that you don’t have the source for. To remove tracing from a function, use untrace(). You can only perform one trace per function, but that one trace can call multiple functions.

22.4.2.4 Call stack

Unfortunately, the call stacks printed by traceback(), browser() & where, and recover() are not consistent. The following table shows how the call stacks from a simple nested set of calls are displayed by the three tools. The numbering is different between traceback() and where, and recover() displays calls in the opposite order.

traceback()	where	recover()	rlang functions
5: stop('...')
4: i(c)	where 1: i(c)	1: f()	1. └─global::f(10)
3: h(b)	where 2: h(b)	2: g(a)	2. └─global::g(a)
2: g(a)	where 3: g(a)	3: h(b)	3. └─global::h(b)
1: f('a')	where 4: f('a')	4: i('a')	4. └─global::i('a')

RStudio displays calls in the same order as traceback(). rlang functions use the same ordering and numbering as recover(), but also use indenting to reinforce the hierarchy of calls.

22.4.3 Compiled code

It is also possible to use an interactive debugger (gdb or lldb) for compiled code (like C or C++). Unfortunately that’s beyond the scope of this book, but there are a few resources that you might find useful:

22.5 Non-interactive debugging

Debugging is most challenging when you can’t run code interactively, typically because it’s part of some pipeline run automatically (possibly on another computer), or because the error doesn’t occur when you run same code interactively. This can be extremely frustrating!

This section will give you some useful tools, but don’t forget the general strategy in Section 22.2. When you can’t explore interactively, it’s particularly important to spend some time making the problem as small as possible so you can iterate quickly. Sometimes callr::r(f, list(1, 2)) can be useful; this calls f(1, 2) in a fresh session, and can help to reproduce the problem.

You might also want to double check for these common issues:

• Is the global environment different? Have you loaded different packages?Are objects left from previous sessions causing differences?

• Is the working directory different?

• Is the PATH environment variable, which determines where externalcommands (like git) are found, different?

• Is the R_LIBS environment variable, which determines where library()looks for packages, different?

22.5.1dump.frames()

dump.frames() is the equivalent to recover() for non-interactive code; it saves a last.dump.rda file in the working directory. Later, an interactive session, you can load('last.dump.rda'); debugger() to enter an interactive debugger with the same interface as recover(). This lets you “cheat”, interactively debugging code that was run non-interactively.

22.5.2 Print debugging

If dump.frames() doesn’t help, a good fallback is print debugging, where you insert numerous print statements to precisely locate the problem, and see the values of important variables. Print debugging is slow and primitive, but it always works, so it’s particularly useful if you can’t get a good traceback. Start by inserting coarse-grained markers, and then make them progressively more fine-grained as you determine exactly where the problem is.

Print debugging is particularly useful for compiled code because it’s not uncommon for the compiler to modify your code to such an extent you can’t figure out the root problem even when inside an interactive debugger.

22.5.3 RMarkdown

Debugging code inside RMarkdown files requires some special tools. First, if you’re knitting the file using RStudio, switch to calling rmarkdown::render('path/to/file.Rmd') instead. This runs the code in the current session, which makes it easier to debug. If doing this makes the problem go away, you’ll need to figure out what makes the environments different.

If the problem persists, you’ll need to use your interactive debugging skills. Whatever method you use, you’ll need an extra step: in the error handler, you’ll need to call sink(). This removes the default sink that knitr uses to capture all output, and ensures that you can see the results in the console. For example, to use recover() with RMarkdown, you’d put the following code in your setup block:

This will generate a “no sink to remove” warning when knitr completes; you can safely ignore this warning.

If you simply want a traceback, the easiest option is to use rlang::trace_back(), taking advantage of the rlang_trace_top_env option. This ensures that you only see the traceback from your code, instead of all the functions called by RMarkdown and knitr.

22.6 Non-error failures

There are other ways for a function to fail apart from throwing an error:

• A function may generate an unexpected warning. The easiest way to track downwarnings is to convert them into errors with options(warn = 2) and use thethe call stack, like doWithOneRestart(), withOneRestart(),regular debugging tools. When you do this you’ll see some extra callswithRestarts(), and .signalSimpleWarning(). Ignore these: they areinternal functions used to turn warnings into errors.

• A function may generate an unexpected message. You can userlang::with_abort() to turn these messages into errors:

• A function might never return. This is particularly hard to debugautomatically, but sometimes terminating the function and looking at thetraceback() is informative. Otherwise, use use print debugging,as in Section 22.5.2.

• The worst scenario is that your code might crash R completely, leaving youwith no way to interactively debug your code. This indicates a bug incompiled (C or C++) code.

  If the bug is in your compiled code, you’ll need to follow the links in Section22.4.3 and learn how to use an interactive C debugger(or insert many print statements).

  If the bug is in a package or base R, you’ll need to contact the packagemaintainer. In either case, work on making the smallest possiblereproducible example (Section 1.7) to help the developer help you.

Before Reporting a Bug

Before you report a bug, please consult the Frequently Asked Questions. Itcontains workarounds for many of the failure conditions for which we know aworkaround. This includes a large fraction of the failures people seem toencounter in practice.

After that, please search Bugzilla to see if the bug has already beenreported. There are two ways to do this:

• Using the Bugzilla query page; choose Valgrind as the 'product', and then type something relevant in the 'words' box. If you are seeing a crash or abort, searching for part of the abort message might be effective. If you are feeling adventurous you can select the 'Advanced search' tab; this gives a lot more control but isn't much better for finding existing bugs.
• Or you can view all open Valgrind bug reports at the Bugzilla all open bugs page, and use your browser's search facilities to search through them.

Note that KDE kindly lets us use their Bugzilla, which explains the URLsof those pages and all the mentions of KDE.

Anyone can search in Bugzilla, you don't need an account. Searchingrequires some effort, but helps avoid duplicates, and you may find that yourproblem has already been solved.

Reporting a Bug

If you haven't encountered your problem after those steps, please file areport using our Bugzilla report page. You need aKDE Bugzilla account to report a bug; instructions for creating one are onthe page. Creating an account takes some time and effort, but it's anecessary evil when using Bugzilla.

The bug report form can be intimidating. Fortunately you don't have tofill in all the fields. Leave all fields blank except the following:

Alternatives To Valgrind On Windows

• Component: If the problem is with a specific Valgrind tool (eg. Memcheck, Cachegrind), select the tool name. If it's a Vex issue (i.e. an abort message mentions 'vex'), select 'vex'. If it's a general problem that appears tool-independent, or you are not sure, select 'general'.
• Version: The version number is shown when Valgrind starts up, on the 'Using valgrind-$VERSION, a dynamic binary instrumentation framework' line. A 'GIT'-suffixed version will only appear if you are using code directly from the git repository.
• Severity: If Valgrind won't compile, choose 'major'. If you are seeing a crash, choose 'crash'. If your problem is minor, choose 'minor' or 'wishlist'. Otherwise, choose 'normal'. Please leave the 'grave' or 'critical' categories to the Valgrind developers to decide.
• Platform: 'unspecified' is usually fine; this field isn't very important unless it's a packaging-related problem.
• OS: This is auto-filled in, but unless you're confident it's an OS-specific problem, it's probably best to change it to 'unspecified'.
• Summary: This is the title of the bug report. Try to make it precise. E.g. if you get an assertion failure, don't say 'assertion failure'; copy in the actual assertion failure message.
• Description: The most important field, which describes the problem. Please include the following information:
  1. The output of uname -a.
  2. The full output you get when you run your program under Valgrind with the -v flag.
  Note that a bug is much more likely to be fixed if a Valgrind developer can reproduce it. So full reproduction steps are very helpful. Small test cases are even better.

Alternative To Valgrind Mac

Here are some resources on how to write a good bug report, which can helpyour get your problem fixed quicker:

• Eric Raymond's and Rick Moen's How To Ask Questions The Smart Way
• mozilla.org's bug writing guidelines
• Simon Tatham's How to Report Bugs Effectively

After Reporting a Bug

All bug reports are read by multiple Valgrind developers. Furthermore,we try to respond to most bug reports, but we have limited time so this doesnot always happen. We may also ask for more information.

If a bug is confirmed (e.g. we are able to reproduce it) we will usuallychange its status from UNCONFIRMED to NEW or ASSIGNED. Important bugs willbe given a 'target' by developers indicating that they are required/desiredfor an upcoming. Note that we don't really use the 'priority' field, so itwill usually be 'NOR' (normal).

Once a bug is fixed in the git repository, it is changed to RESOLVED. Wedo not use the VERIFIED or CLOSED statuses.

Some bugs are fixed quickly, some take a long time to get fixed, some arenever fixed. Please be patient if your bug is not acted upon quickly. Onegreat thing about Bugzilla is that, at the very least, bug reports do notget lost.

Alternatives

Alternatives To Valgrind

If you have trouble with Bugzilla, or for some reason youdon't think Bugzilla is appropriate for your report (although itprobably is), contact the valgrind-users mailing list. But you may just be told to file a bug in Bugzilla.