Vger broken w.r.t. gdb

[Paul Mackerras]

Daniel Jacobowitz <drow at false.org> wrote:

> Now I'm really confused.
> 
> >From my readings it appears that we should only reach this point if a
> trap instruction was encountered.  But from what I can see no trap
> instruction exists at that address.  At

A common thing that gdb does is to put trap instructions into the
memory image of a process being debugged.  It sounds to me as though,
with all the page cache and memory management changes that have gone
on in 2.3, we now have the undesirable situation that a trap
instruction put in by gdb hasn't stayed confined to the process being
debugged but has leaked into the copy of the page that is being used
by other processes.

> Perhaps something having to do with instruction caching by the
> processor?  This is a completely wild guess, but if a trap instruction
> was encountered, and then gdb cleared it, and the instruction cache was
> not flushed...

Well, whatever the problem is, it's something new in 2.3, it's not a
long-standing omission of some cache flushing stuff.  It's far more
likely to be something in the ptrace syscall code which hasn't been
correctly updated to cope with the recent page cache and VM changes.

Paul.

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]