Bug#777731: chromium-dbg: Incomplete debug symbols

2015-03-06 Thread Michael Gilbert
On Fri, Mar 6, 2015 at 4:57 PM, Paul Menzel wrote: > No, I did not. So to create meaningful stack/back traces for > non-reproducible issues, I need to pass the switch `--debug` at every > start? Is that correct? Well, --debug helps by automatically making sure you have the right paths set (you cou

Bug#777731: chromium-dbg: Incomplete debug symbols

2015-03-06 Thread Paul Menzel
Am Samstag, den 21.02.2015, 22:59 -0500 schrieb Michael Gilbert: […] > Did you use "chromium --debug"? If not gdb by itself won't be enough. No, I did not. So to create meaningful stack/back traces for non-reproducible issues, I need to pass the switch `--debug` at every start? Is that correct?

Bug#777731: chromium-dbg: Incomplete debug symbols

2015-02-21 Thread Michael Gilbert
control: tag -1 moreinfo control: severity -1 minor Did you use "chromium --debug"? If not gdb by itself won't be enough. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777731: chromium-dbg: Incomplete debug symbols

2015-02-11 Thread Paul Menzel
Package: chromium-dbg Version: 40.0.2214.91-1 Severity: normal Dear Debian folks, Chromium crashed today and I wanted to create a meaningfull backtrace. NetworkChangeNo[1138]: segfault at fff4 ip b2100217 sp ad6e8c20 error 5 in chromium[b172e000+60bb000] Wanting to create a meanin