On Fri, Jul 22, 2016 at 04:39:00PM -0700, Andy Lutomirski wrote:
> On Fri, Jul 22, 2016 at 4:30 PM, Josh Poimboeuf wrote:
> > On Fri, Jul 22, 2016 at 04:18:04PM -0700, Andy Lutomirski wrote:
> >> On Fri, Jul 22, 2016 at 3:20 PM, Josh Poimboeuf
> >> wrote:
> >> > On Fri, Jul 22, 2016 at 02:46:10P
On Fri, Jul 22, 2016 at 4:30 PM, Josh Poimboeuf wrote:
> On Fri, Jul 22, 2016 at 04:18:04PM -0700, Andy Lutomirski wrote:
>> On Fri, Jul 22, 2016 at 3:20 PM, Josh Poimboeuf wrote:
>> > On Fri, Jul 22, 2016 at 02:46:10PM -0700, Andy Lutomirski wrote:
>> >> On Fri, Jul 22, 2016 at 8:57 AM, Josh Poi
On Fri, Jul 22, 2016 at 04:18:04PM -0700, Andy Lutomirski wrote:
> On Fri, Jul 22, 2016 at 3:20 PM, Josh Poimboeuf wrote:
> > On Fri, Jul 22, 2016 at 02:46:10PM -0700, Andy Lutomirski wrote:
> >> On Fri, Jul 22, 2016 at 8:57 AM, Josh Poimboeuf
> >> wrote:
> >> > On Thu, Jul 21, 2016 at 10:13:03P
On Fri, Jul 22, 2016 at 3:20 PM, Josh Poimboeuf wrote:
> On Fri, Jul 22, 2016 at 02:46:10PM -0700, Andy Lutomirski wrote:
>> On Fri, Jul 22, 2016 at 8:57 AM, Josh Poimboeuf wrote:
>> > On Thu, Jul 21, 2016 at 10:13:03PM -0700, Andy Lutomirski wrote:
>> >> On Thu, Jul 21, 2016 at 8:30 PM, Josh Poi
On Fri, Jul 22, 2016 at 02:46:10PM -0700, Andy Lutomirski wrote:
> On Fri, Jul 22, 2016 at 8:57 AM, Josh Poimboeuf wrote:
> > On Thu, Jul 21, 2016 at 10:13:03PM -0700, Andy Lutomirski wrote:
> >> On Thu, Jul 21, 2016 at 8:30 PM, Josh Poimboeuf
> >> wrote:
> >> > On Thu, Jul 21, 2016 at 03:32:32P
On Fri, Jul 22, 2016 at 8:57 AM, Josh Poimboeuf wrote:
> On Thu, Jul 21, 2016 at 10:13:03PM -0700, Andy Lutomirski wrote:
>> On Thu, Jul 21, 2016 at 8:30 PM, Josh Poimboeuf wrote:
>> > On Thu, Jul 21, 2016 at 03:32:32PM -0700, Andy Lutomirski wrote:
>> >> On Thu, Jul 21, 2016 at 2:21 PM, Josh Poi
On Thu, Jul 21, 2016 at 10:13:03PM -0700, Andy Lutomirski wrote:
> On Thu, Jul 21, 2016 at 8:30 PM, Josh Poimboeuf wrote:
> > On Thu, Jul 21, 2016 at 03:32:32PM -0700, Andy Lutomirski wrote:
> >> On Thu, Jul 21, 2016 at 2:21 PM, Josh Poimboeuf
> >> wrote:
> >> > Now that we can find pt_regs regi
On Thu, Jul 21, 2016 at 8:30 PM, Josh Poimboeuf wrote:
> On Thu, Jul 21, 2016 at 03:32:32PM -0700, Andy Lutomirski wrote:
>> On Thu, Jul 21, 2016 at 2:21 PM, Josh Poimboeuf wrote:
>> > Now that we can find pt_regs registers in the middle of the stack due to
>> > an interrupt or exception, we can
On Thu, Jul 21, 2016 at 03:32:32PM -0700, Andy Lutomirski wrote:
> On Thu, Jul 21, 2016 at 2:21 PM, Josh Poimboeuf wrote:
> > Now that we can find pt_regs registers in the middle of the stack due to
> > an interrupt or exception, we can print them. Here's what it looks
> > like:
> >
> >...
>
On Thu, Jul 21, 2016 at 2:21 PM, Josh Poimboeuf wrote:
> Now that we can find pt_regs registers in the middle of the stack due to
> an interrupt or exception, we can print them. Here's what it looks
> like:
>
>...
>[] do_async_page_fault+0x2c/0xa0
>[] async_page_fault+0x28/0x30
> RI
Now that we can find pt_regs registers in the middle of the stack due to
an interrupt or exception, we can print them. Here's what it looks
like:
...
[] do_async_page_fault+0x2c/0xa0
[] async_page_fault+0x28/0x30
RIP: 0010:[] [] __clear_user+0x42/0x70
RSP: 0018:88007876fd38 EFL
11 matches
Mail list logo
