[jira] [Created] (MYNEWT-172) Debugging sim target on Linux is challenging
Gordon Chaffee created MYNEWT-172:
-
Summary: Debugging 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
When using gdb to debug, step over works unreliably 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 ) 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)
[jira] [Updated] (MYNEWT-172) gdb debugging of sim target on Linux is challenging
[
https://issues.apache.org/jira/browse/MYNEWT-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Chaffee updated MYNEWT-172:
--
Description:
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 ) 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)
was:
When using gdb to debug, step over works unreliably 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 ) 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)
> 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
>
> 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 ) 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)
[jira] [Created] (MYNEWT-168) Understanding Newt Terms in the Getting Started guides should be "Newt Walkthrough"
Sterling Hughes created MYNEWT-168: -- Summary: Understanding Newt Terms in the Getting Started guides should be "Newt Walkthrough" Key: MYNEWT-168 URL: https://issues.apache.org/jira/browse/MYNEWT-168 Project: Mynewt Issue Type: Improvement Reporter: Sterling Hughes And should represent a walkthrough of the high level Newt components, with links on where to find more in-depth information on each of them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MYNEWT-166) Documentation should maintain sidebar when scrolling
Sterling Hughes created MYNEWT-166: -- Summary: Documentation should maintain sidebar when scrolling Key: MYNEWT-166 URL: https://issues.apache.org/jira/browse/MYNEWT-166 Project: Mynewt Issue Type: Improvement Components: Documentation Reporter: Sterling Hughes Assignee: Aditi Hilbert Right now, when you scroll on the documentation, the sidebar disappears but the top bar remains fixed. This was changed when the bottom bar was moved to the bottom of the window. I think the previous layout was desirable, however, the sidebar should be extended the length of any window it's being displayed on. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MYNEWT-167) Newt sometimes performs unnecessary compiles due to inconsistently ordered cflags
[ https://issues.apache.org/jira/browse/MYNEWT-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Collins updated MYNEWT-167: --- Fix Version/s: v0_8_0_beta2 > Newt sometimes performs unnecessary compiles due to inconsistently ordered > cflags > - > > Key: MYNEWT-167 > URL: https://issues.apache.org/jira/browse/MYNEWT-167 > Project: Mynewt > Issue Type: Bug > Components: Newt >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v0_8_0_beta2 > > > The cflags, lflags, and aflags that get passed to the compiler are not always > consistently ordered between builds. If the compiler invocation is different > from the previous one, newt forces a recompile. If the only thing that has > changed is the order of the flags, then such a recompile is unnecessary. > The fix is to sort the flags alphabetically. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
