| Summary: | udhcpc6 and ping6 : alignment trap | ||
|---|---|---|---|
| Product: | Busybox | Reporter: | redongjun |
| Component: | Networking | Assignee: | unassigned |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | critical | CC: | busybox-cvs |
| Priority: | P5 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Linux | ||
| Host: | Target: | ||
| Build: | |||
|
Description
redongjun
2012-11-02 02:29:46 UTC
It is impossible to find problem by absolute instruction address without have exactly the same binaries. You should use addr2line utility against busybox_unstripped binary, compiled with debug symbols (-g3 best of all). For example: addr2line -f -e busybox_unstripped 0x0415040 ping6_main .../busybox/networking/ping.c:882 udhcpc6 is not production-ready. It waits for someone to develop it further. I don't think we'll get more info in this bug report. |