Bug 209239 - www/netsurf -3.5 Program received signal SIGBUS, Bus error on ARM
Summary: www/netsurf -3.5 Program received signal SIGBUS, Bus error on ARM
Status: Closed Feedback Timeout
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: arm Any
: --- Affects Some People
Assignee: Walter Schwarzenfeld
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-03 16:31 UTC by Ulrich Grey
Modified: 2018-03-10 21:26 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (olivierd)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ulrich Grey 2016-05-03 16:31:03 UTC 
11.0-CURRENT FreeBSD 11.0-CURRENT #0 r297692 IMX6 arm

gwgpi@wqtest:~ % gdb /usr/local/bin/netsurf-gtk 
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "armv6-marcel-freebsd"...(no debugging symbols found)...
(gdb) run
Starting program: /usr/local/bin/netsurf-gtk 
[New LWP 100108]
[New Thread 22411000 (LWP 100108/netsurf-gtk)]
[New Thread 22411300 (LWP 100246/netsurf-gtk)]

Program received signal SIGBUS, Bus error.
[Switching to Thread 22411000 (LWP 100108/netsurf-gtk)]
0x002adb18 in nsurl_parent ()
Current language:  auto; currently minimal
(gdb) where
#0  0x002adb18 in nsurl_parent ()
#1  0x002c2dd4 in content_status_name ()
#2  0x002c2dd4 in content_status_name ()
(gdb) disassemble $pc-16 $pc+16
Dump of assembler code from 0x2adb08 to 0x2adb28:
0x002adb08 <nsurl_parent+3188>: str     r0, [sp]
0x002adb0c <nsurl_parent+3192>: bl      0x2adb3c <nsurl_parent+3240>
0x002adb10 <nsurl_parent+3196>: ldr     lr, [sp]
0x002adb14 <nsurl_parent+3200>: add     r0, r0, lr, lsl #2
0x002adb18 <nsurl_parent+3204>: ldr     r0, [r0, #52]
0x002adb1c <nsurl_parent+3208>: ldr     lr, [r11, #-8]
0x002adb20 <nsurl_parent+3212>: and     r0, r0, lr
0x002adb24 <nsurl_parent+3216>: str     r0, [sp, #4]
End of assembler dump.
(gdb) info registers
r0             0x1c9    457
r1             0x100    256
r2             0x8000   32768
r3             0x72     114
r4             0xbfbfd460       -1077947296
r5             0x0      0
r6             0x2c2dd4 2895316
r7             0x216ad9bc       560650684
r8             0x1      1
r9             0x21dc5408       568087560
r10            0x2245a640       574989888
r11            0xbfbfd328       -1077947608
r12            0x5c     92
sp             0xbfbfd310       -1077947632
lr             0x72     114
pc             0x2adb18 2808600
fps            0xbfbfe3e0       -1077943328
cpsr           0x20000010       536870928
(gdb) The program is running.  Exit anyway? (y or n) y
Comment 1 Rene Ladan freebsd_committer freebsd_triage 2017-03-19 13:48:58 UTC 
reset assignee
Comment 2 Walter Schwarzenfeld freebsd_triage 2018-01-16 13:27:07 UTC 
We have version 3.7. Does the problem still exists?
Comment 3 Walter Schwarzenfeld freebsd_triage 2018-03-10 21:26:09 UTC 
Close here, feedback timeout. If there are still problems with newer versions, please reopen or better file a new PR.