search for: steppable

...(at least in clang)? The debug info generated by gcc, llvm-gcc or clang doesn't deal with macros in a way that would allow single-stepping through them. -g3 in gcc allows me to expand a macro from gcc, but thats it, as far as debugging is concerned it acts like a single instruction, not single-steppable. I generally tend to avoid the use of macros that do something non-trivial (i.e. requires debugging), but unfortunately C doesn't support templates, so in some situations I am forced to use macros, instead of functions. Best regards, --Edwin

On 04/11/2017 07:50 AM, Andrew Holway wrote: >> I'd much rather have a bash script to look at-- and manually step through. > > Is that a joke? Bash is an almighty impenetrable nightmare. I've been doing > *nix for nearly 10 years and *still* am unable to read anything vaguely > complicated in bash whereas I can write fairly decent python after 6 > months. From my

Hi All, Today, debugging information is encoded in LLVM IR using various llvm.dbg intrinsics, such as llvm.dbg.stoppoint. For exmaple, !1 = metadata !{i32 458769, i32 0, i32 12, metadata !"foo.c", metadata !"/tmp", metadata !"clang 1.0", i1 true, i1 false, metadata !"", i32 0} ... call void @llvm.dbg.stoppoint(i32 5, i32 5, metadata !1) store i32