This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFA] Patch to fix reverse return from subroutine error


> -         || execution_direction == EXEC_REVERSE))
> +         || (execution_direction == EXEC_REVERSE
> +             && ecs->event_thread->step_frame_id.stack_addr_p
> +             && get_frame_id (get_current_frame ()).stack_addr_p
> +              && !gdbarch_inner_than (current_gdbarch,
> +                                     ecs->event_thread->step_frame_id.stack_addr,
> +                                     get_frame_id

Sorry to pitch in so late, but this doesn't look right to me.
Common code shouldn't be accessing frame id members directly, frame ids
are supposed to be opaque.  What is this trying to do?

-- 
Pedro Alves


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]