On Mon, May 14, 2018 at 08:08:45PM +0900, Bryan Linton wrote: > On 2018-05-13 12:01:52, Landry Breuil <lan...@openbsd.org> wrote: > > > > Sadly, this trace doesnt really help, since it seems to be a signal > > handler that catches the SIGABRT, or the signal handler is in the main > > process and the abort is in the content process, and not the trace of > > the codepath that triggers this SIGABRT... > > > > How about trying it live (if you can) within egdb following all > > processes, with a breakpoint on signal or SYS_access ? > > > > Hello, > > I tried to run firefox in egdb but I'm having some difficulty. > egdb seems to crash and then takes my entire system down with it. > Mouse, keyboard, CTRL+ALT+DEL, CTRL+ALT+BKSP, all stop working. > > I saw your recent mail to ports@ about how to help debug the new > pledged firefox, and what other info may help too (ktrace etc.). > > I'll try to see if I can figure out why egdb is crashing and > provide some more information soon, but I may not be able to do so > until this weekend. (The first thing I'll try is updating to a > newer snapshot.) > > Until then, please don't let this bug report hold you back from > doing any work you had planned. For the meantime at least, > firefox runs fine with the getpw pledge added. That and the fact > that I seem to be the only one experiencing this crash tells me > that this bug is probably only affecting me at the moment.
I've had several ppl reporting me this one, but so far none provided enough convincing info *why* it was needed. I have zero issues saving files/images when pledged without getpw. And besides regular updates (started working on 61.0 beta), i have no work planned on this on the short term. This is taking way too much of my spare time.
