# Unable to launch debugger

**URL:** <https://forum.sierrawireless.com/t/unable-to-launch-debugger/5668>\
**Category:** Development tools\
**Created:** [June 18, 2012, 9:38pm UTC](https://forum.sierrawireless.com/t/unable-to-launch-debugger/5668 "2012-06-18T21:38:26Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![dsk\_5](https://avatars.discourse-cdn.com/v4/letter/d/c67d28/32.png) [@dsk\_5](https://forum.sierrawireless.com/u/dsk_5)\
**Post date:** [June 18, 2012, 9:38pm UTC](https://forum.sierrawireless.com/t/unable-to-launch-debugger/5668/1 "2012-06-18T21:38:26Z")

</div>

We’re getting the error message below when trying to debug using DS 2.2.0:

Error while launching command: gdb --version

There is no further information available if you click Details. Is there some configuration item that’s not set correctly?

---

<div class="post-metadata">

**Author:** ![daav](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/daav/32/2767_2.png) [@daav](https://forum.sierrawireless.com/u/daav)\
**Post date:** [June 19, 2012, 7:39am UTC](https://forum.sierrawireless.com/t/unable-to-launch-debugger/5668/2 "2012-06-19T07:39:02Z")

</div>

Sounds like a mistake in your launch configuration: DS should try to invoke arm-elf-gdb, and not simply gdb.  
You should have a read of this topic: [https://forum.sierrawireless.com/t/cannot-debug-in-embedded-gdb-mode/5088/1](https://forum.sierrawireless.com/t/cannot-debug-in-embedded-gdb-mode/5088/1)

---

<div class="post-metadata">

**Author:** ![dsk\_5](https://avatars.discourse-cdn.com/v4/letter/d/c67d28/32.png) [@dsk\_5](https://forum.sierrawireless.com/u/dsk_5)\
**Post date:** [June 19, 2012, 1:57pm UTC](https://forum.sierrawireless.com/t/unable-to-launch-debugger/5668/3 "2012-06-19T13:57:09Z")

</div>

Ok, we’ve entered arm-elf-gdb as the debugging app, but are now getting the error “Load model element: Tasks status =\> ERROR:java.lang.Integer cannot be cast to java.lang.String” (full details from the error popup are in the attached zip file.

We also get this error whenever opening a com port or downloading a file in DS, however neither of these errors have caused any problems that we’ve observed.

---

<div class="post-metadata">

**Author:** ![daav](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/daav/32/2767_2.png) [@daav](https://forum.sierrawireless.com/u/daav)\
**Post date:** [June 20, 2012, 6:36am UTC](https://forum.sierrawireless.com/t/unable-to-launch-debugger/5668/4 "2012-06-20T06:36:55Z")

</div>

We need to have more details to diagnose the issue: please can you use the Help \> Build Technical Report feature, export it and attach the zip file here?

---

<div class="post-metadata">

**Author:** ![dsk\_5](https://avatars.discourse-cdn.com/v4/letter/d/c67d28/32.png) [@dsk\_5](https://forum.sierrawireless.com/u/dsk_5)\
**Post date:** [June 20, 2012, 2:11pm UTC](https://forum.sierrawireless.com/t/unable-to-launch-debugger/5668/5 "2012-06-20T14:11:28Z")

</div>

> [@daav](#):
>
> can you use the Help \> Build Technical Report feature, export it and attach the zip file here?

I don’t see this feature. Attached is what is in my Help menu. Note I created a simple hello world test app to see if we had the same problem with a different application, and we do.

---

<div class="post-metadata">

**Author:** ![daav](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/daav/32/2767_2.png) [@daav](https://forum.sierrawireless.com/u/daav)\
**Post date:** [June 21, 2012, 8:49am UTC](https://forum.sierrawireless.com/t/unable-to-launch-debugger/5668/6 "2012-06-21T08:49:15Z")

</div>

The option is available from DS 2.2.0  
Please can you upgrade, and first check if it fixes your issue?  
And if not, please send the technical report.

---

<div class="post-metadata">

**Author:** ![dsk\_5](https://avatars.discourse-cdn.com/v4/letter/d/c67d28/32.png) [@dsk\_5](https://forum.sierrawireless.com/u/dsk_5)\
**Post date:** [June 21, 2012, 2:21pm UTC](https://forum.sierrawireless.com/t/unable-to-launch-debugger/5668/7 "2012-06-21T14:21:25Z")

</div>

> [@daav](#):
>
> The option is available from DS 2.2.0

We are using 2.2.0 (I should have mentioned that in my previous post). Attached is some of the information provided when selecting Help-\>About-\>Installation Details, which I assume is much the same as what would be dislayed by the Technical Report feature.

I guess the next step is to reinstall 2.2.0. I was hoping to avoid that.

\*Update: Tried to reinstall DS, and couldn’t even get it to start afterwards (which didn’t surprise me, almost every time there is an upgade or some change made, something breaks) Was able to do a system restore and get things back to the way they were (i.e. with a non-functional debugger, but everything else working).

---

<div class="post-metadata">

**Author:** ![daav](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/daav/32/2767_2.png) [@daav](https://forum.sierrawireless.com/u/daav)\
**Post date:** [June 25, 2012, 10:48am UTC](https://forum.sierrawireless.com/t/unable-to-launch-debugger/5668/8 "2012-06-25T10:48:56Z")

</div>

Seen that you have a “Patch for Target Manager” installed: please uninstall it. This should fix some issues concerning the target management perspective.
