# How to use dlv to debug beats with version 6.7.0+

**URL:** <https://discuss.elastic.co/t/how-to-use-dlv-to-debug-beats-with-version-6-7-0/180449>\
**Category:** Beats\
**Created:** [May 9, 2019, 10:39pm UTC](https://discuss.elastic.co/t/how-to-use-dlv-to-debug-beats-with-version-6-7-0/180449 "2019-05-09T22:39:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rugang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rugang/32/122315_2.png) [@rugang](https://discuss.elastic.co/u/rugang)\
**Post date:** [May 9, 2019, 10:39pm UTC](https://discuss.elastic.co/t/how-to-use-dlv-to-debug-beats-with-version-6-7-0/180449/1 "2019-05-09T22:39:25Z")

</div>

I'm using beats version 6.7.0, it has 1.10.8 in .go-version, so I use go 1.10.8 to build it.  
Building is fine and binaries run well.

But when I try to use dlv to debug a beat binary (auditbeat), it shows to me:

could not launch process: could not get .debug\_frame section: could not find .debug\_frame section

googled and found the reason could be beats uses plugin and go version \> 1.10 won't have .debug\_frame in binary if plugin is used.  
here's a link [( missing debug\_frame section if package plugin is imported)](https://github.com/golang/go/issues/23733) for this issue.  
Another link [( support eh\_frame if debug\_frame is not present)](https://github.com/go-delve/delve/issues/1118) for the issue

I tried to write a simple go package without plugin, dlv runs well on it.

So my question is, how to debug beats codes (version \> 6.7.0)

I tried to use go 1.12.4 to build beats 6.7.0, same issue.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 7, 2019, 12:39am UTC](https://discuss.elastic.co/t/how-to-use-dlv-to-debug-beats-with-version-6-7-0/180449/2 "2019-06-07T00:39:27Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
