title: Is it possible to step into the expanded Macro when use CLion debugging Rust project
body: <p>In Rust IDE CLion, Now, when debugging step by step, if the code is a piece of Macro. CLoin will not expand and go into the Macro. The debugging cursor pointed to the code is jumping on the Macro repeatedly. So users can't know the authentic execute code。The ·cargo expand· is like a static tool, but it can't integrate into debugging.</p>
  <p>Is it possible to step into the expanded Macro when use CLion debugging rust project.</p>
  <p>Make the debugging journey like going through line by line in the expanded Macro happily?</p>
  <p>Update 1: CLion will expand the Macro automatically, Is the expanded file cached for compiling? If a bin is debuggable, the bin must have symbol info, Is it possible when do step debugging, tools like CLion, gdb or lldb can point the current debugging line to the expanded file or the raw source code file(option by user) by finding clue the symbol?</p>
  <p>Update 2: Sometimes, My program got a panic. From the stacktrace, I got a file named like '/sfwerasdf2323r.rs', I opened it in the editor, I think it's an auto-expanded file by CLion. I tried to &quot;open in&quot; from the context menu of the file to find it out in the <code>File explorer</code>(or <code>Finder</code>), but CLion shows: <code>open in -&gt; nowhere</code>. Is this file a cache in memory? Is it not in a <code>/tmp</code> folder?</p>
  <p>This makes me believe that it is possible to debug in the expanded file. CLion maybe need to do a further more is to format the auto-expanded file</p>