Re: mipsbe solib event breakpoint endian?

["Kris Warkentin" <kewarken@qnx.com>]

Finally got around to chasing this again and I've found the problem.  I'm
hoping someone might be able to explain why I'm seeing what I'm seeing.

GDB-5.2.1 targetting QNX MipsBE:
Breakpoint 4, enable_break () at ../../gdb/solib-svr4.c:939
939           if (!load_addr_found)
(top) n
940             load_addr = read_pc () - tmp_bfd->start_address;
(top) p read_pc()
$1 = 1882417036
(top) p /x read_pc()
$2 = 0x7033678c
(top)


GDB-HEAD targetting QNX MipsBE:
Breakpoint 3, enable_break () at ../../gdb/solib-svr4.c:1039
1039            load_addr = read_pc () - tmp_bfd->start_address;
(top) p read_pc()
$1 = 8084919611063009279
(top) p /x read_pc()
$2 = 0x7033678ceeffffff
(top)

Looks like someone thinks the program counter is a 64 bit value....  Any
hints?

cheers,

Kris

> On Jul 3, 11:00am, Kris Warkentin wrote:
>
> > I'm having a problem with debugging on a mips big endian target.  Mipsle
> > works fine but on mipsbe it looks like the solib-event breakpoint is
> > cross-endian.  I don't have a target available right at this moment to
show
> > you the exact output but it's trying to set the breakpoint at some
freaking
> > huge number that doesn't look right at all.  I'm assuming that it's
reading
> > the memory from the target but not flipping it for some reason.  Now
> > obviously this works for PowerPC so the functionality must be there.
> >
> > Can anyone tell me if I'm barking up the wrong tree?
>
> I've done some work on MIPS recently and do not recall seeing this
> kind of problem.
>
> Kevin
>