[jira] [Resolved] (MYNEWT-172) gdb debugging of sim target on Linux is challenging

["Marko Kiiskila (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MYNEWT-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marko Kiiskila resolved MYNEWT-172.
-----------------------------------
       Resolution: Fixed
         Assignee: Marko Kiiskila
    Fix Version/s: v0_10_0

This should be better now. 'newt run' for native targets runs gdb script which adds hooks to turn off SIGALRM signals while stopped. This should allow single stepping without going via signal handler due to timer ticks.

> gdb debugging of sim target on Linux is challenging
> ---------------------------------------------------
>
>                 Key: MYNEWT-172
>                 URL: https://issues.apache.org/jira/browse/MYNEWT-172
>             Project: Mynewt
>          Issue Type: Bug
>          Components: OS
>    Affects Versions: v0_8_0_beta1
>         Environment: Linux ubuntu 3.13.0-77-generic (Ubuntu 14.04)
>            Reporter: Gordon Chaffee
>            Assignee: Marko Kiiskila
>             Fix For: v0_10_0
>
>
> When using gdb to debug, step over works unreliably when the context switches in the middle of the execution. This is on a Linux system. Example:
> gdb ./project/slinky/bin/slinky/slinky.elf
> (gdb) b log_nmgr_append
> Breakpoint 1 at 0x804a275: file log_nmgr.c, line 144.
> (gdb) run
> Breakpoint 1, log_nmgr_append (njb=0x806a5c0 <nmgr_task_jbuf>) at log_nmgr.c:144
> 144	{
> (gdb) n
> 145	    char msg_str[256] = {0};
> (gdb) n
> Warning:
> Cannot insert breakpoint 0.
> Cannot access memory at address 0x34e37066
> 0xf7e3d1d1 in siglongjmp () from /lib32/libc.so.6
> (gdb) 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)