|
From: Maynard J. <may...@us...> - 2011-10-27 19:16:48
|
On 10/22/2011 2:04 AM, Philippe Waroquiers wrote: > >> By the way, I was able to successfully run mcsigpass manually (one session for >> valgrind and one session for gdb) using mcsigpass.stdinB.gdb >> as input to the gdb session, so I *think* I'm running the two processes >> correctly in manual mode. Any idea what I'm doing wrong? >> I'm not versed in using gdbserver, so it's very possible I'm missing something. > > IIUC, these tests are ok on fedora16/Power7 and not ok on suse11/power7. Yes. > One thing you can try is to do the same commands as in the stdinB.gdb but with > the standard gdbserver > part of the gdb distribution, and see if this also fails to put the breakpoints. I can set breakpoints OK when using gdbserver manually, outside of valgrind. > > I can take a look at the problem if you run the following commands on both > platforms, Well, the Fedora16/ppc64 box I had access to was freshly installed with F16 alpha yesterday. I pulled valgrind from svn and built it and tried to run the gdbserver tests. I don't know what's changed (since the gdbserver tests had run quite well on Fedora the last I tried), but I had major problems. The testcases either hung or failed the pre-req because gdb.step does not exist. sigh.... -Maynard > and send the gdbserver_tests/*.out files. > > rm gdbserver_tests/*.out > perl tests/vg_regtest --keep-unfiltered gdbserver_tests/mcinfcallRU.vgtest > .... send the gdbserver_tests/*.out > > export EXTRA_REGTEST_OPTS="-v -v -d -d -d" > .... redo the above > > Thanks > > |