On Thu, Aug 22, 2019 at 9:53 AM Rick Payne <[email protected]> wrote:
> On Wed, 2019-08-21 at 13:21 +0300, Nadav Har'El wrote: > > > > This is often not the problem itself, but rather a result of an > > earlier bug, which caused > > us to want to print an error message and that generated another > > error, and so on. > > Understood. > > Still working on testing 0.53, and I'm now seeing another page fault > issue: > > page fault outsAssertion failed: sched::exception_depth <= 1 > (core/sched.cc: reschedule_from_interrupt: 236) > > [backtrace] > > > I get nothing more than that - no backtrace. Will work on getting a bit > more later. Could well be that I'm running this out of memory too... > Do you know how to get a backtrace from gdb? These sort of failures are almost always some sort of nested failure - for example we have a page fault and while handling this page fault we try to print a message and get a second crash, or something like that. So the message you see doesn't really tell you what was the first thing that went wrong. A backtrace from gdb is usually more helpful. > Rick > > -- You received this message because you are subscribed to the Google Groups "OSv Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/osv-dev/CANEVyjuUjrJ9mwGBKdXFG7NH9GoH%3D92JUitZuKdn2KMXCotwKg%40mail.gmail.com.
