netsurf-develop

[Netsurf-develop] A crash

[Jess H. <gr...@je...>]

Netsurf just crashed, I saved a log. What is the correct procedure in 
this case? (I am dubious about just creating a new bug report, because 
it may already be reported, I can't tell, since from my perspective it 
just crashed.) The same link loaded fine on a second attempt.

I have included a few lines of the log in case it is enough to help.

top:

desktop/netsurf.c netsurf_init 70: version 'Test Build (20 Apr 2007 
19:15)'
desktop/netsurf.c netsurf_init 77: NetSurf on <RISC OS>, node 
<Vigor10>, release <5.11>, version <1.0>, machine <armv5l>

bottom:

confirm_overwrite:1
url_path:NetSurf:URL
url_save:<Choices$Write>.WWW.NetSurf.URL
hotlist_path:NetSurf:Hotlist
hotlist_save:<Choices$Write>.WWW.NetSurf.Hotlist
recent_path:NetSurf:Recent
recent_save:<Choices$Write>.WWW.NetSurf.Recent
theme_path:NetSurf:Themes
theme_save:<Choices$Write>.WWW.NetSurf.Themes
thumbnail_iconise:1

Fatal signal received: Segmentation fault

Stack backtrace:

Running thread 0x2e26e4
  (  31eea4) pc:   15e4c0 lr:   252520 sp:   31eea8  
__write_backtrace()
  (  31eed4) pc:   252378 lr:     8868 sp:   31eed8  ^ro_gui_signal()
  (  31eefc) pc:     8858 lr:   1ce59c sp:   31ef00  
__unixlib_exec_sig()
  (  31efa0) pc:   1cdf50 lr:   2ca630 sp:   31efa4  
__unixlib_raise_signal()
  (  31efb0) pc:   2ca540 lr:    74c5c sp:   31dc68  __h_cback()
  (  31dc74) pc:   239bfc lr:    74c5c sp:   31dc78  
^browser_window_set_status()
  (  31dde0) pc:    74240 lr:    6e3d8 sp:   31dde4  
^browser_window_mouse_action_html()
  (  31de04) pc:    6e384 lr:   155338 sp:   31de08  
browser_window_mouse_click()
  (  31de24) pc:   15529c lr:   20ba40 sp:   31de28  
^ro_gui_window_click()
  (  31de90) pc:   20ba04 lr:   252838 sp:   31de94  
ro_gui_wimp_event_mouse_click()
  (  31dea0) pc:   252788 lr:   2526d4 sp:   31dea4  
^ro_gui_handle_event()
  (  31dfb8) pc:   2525a4 lr:   1bd180 sp:   31dfbc  gui_poll()
  (  31dfc8) pc:   1bd168 lr:   13a6dc sp:   31dfcc  ^netsurf_poll()
  (  31dfe0) pc:   13a694 lr:    b7504 sp:   31dfe4  main()
  (  31dff0) pc:    b74e4 lr:     aee8 sp:   31dff4  _main()


-- 
Jess                   Iyonix
contact http://jess.itworkshop-nexus.net
mailto:gr...@je...

Re: [Netsurf-develop] A crash

[Richard P. <ri...@mi...>]

On 23 Apr 2007 Jess Hampshire wrote:

> Netsurf just crashed, I saved a log. What is the correct procedure in
> this case? (I am dubious about just creating a new bug report, because
> it may already be reported, I can't tell, since from my perspective it
> just crashed.) The same link loaded fine on a second attempt.

1. Scan the existing bug reports in case the problem has already been 
reported. If necessary just add a comment.

2. If it looks like a new bug just raise a bug report and upload the 
log as a zip archive. The developers will close the bug report if it 
turns out to be a duplicate. In the case of a random crash like this 
you won't know.

-- 
 _
|_|. _   Richard Porter               http://www.minijem.plus.com/
|\_||_                                mailto:ri...@mi...

Re: [Netsurf-develop] A crash

[Rob K. <rj...@ne...>]

Jess Hampshire wrote:
>  
> Netsurf just crashed, I saved a log. What is the correct procedure in 
> this case? (I am dubious about just creating a new bug report, because 
> it may already be reported, I can't tell, since from my perspective it 
> just crashed.) The same link loaded fine on a second attempt.

If you are unsure if the cause of a crash has already been reported,
report a new bug.  The developers are in a better position to check for
duplicates, and will close your bug if it has been covered elsewhere.

B.

Re: [Netsurf-develop] A crash

[Jess H. <gr...@je...>]

In message <462...@ne...>
          Rob Kendrick <rj...@ne...> wrote:

> 
> Jess Hampshire wrote:
>> 
>> Netsurf just crashed, I saved a log. What is the correct procedure in
>> this case? (I am dubious about just creating a new bug report, because
>> it may already be reported, I can't tell, since from my perspective it
>> just crashed.) The same link loaded fine on a second attempt.
> 
> If you are unsure if the cause of a crash has already been reported,
> report a new bug.  The developers are in a better position to check for
> duplicates, and will close your bug if it has been covered elsewhere.

Done.


-- 
Jess                   Iyonix
contact http://jess.itworkshop-nexus.net
mailto:gr...@je...