This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/18208] Fails in gdb.base/coredump-filter.exp in remote testing
- From: "qiyao at gcc dot gnu.org" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Wed, 08 Apr 2015 12:00:03 +0000
- Subject: [Bug gdb/18208] Fails in gdb.base/coredump-filter.exp in remote testing
- Auto-submitted: auto-generated
- References: <bug-18208-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18208
--- Comment #5 from Yao Qi <qiyao at gcc dot gnu.org> ---
I am running testing for aarch64-linux-gnu target on x86_64 machine, and they
are connected via ssh.
After this remote_exec,
remote_exec target "sh -c \"echo $filter_flag > /proc/$ipid/coredump_filter\""
I dump the /proc/$ipid/coredump_filter via cat, and it becomes 00000000, which
is a surprise to me. Dejagnu does remote_exec on build like this,
$ ssh -l yaoqi01 linaro-junor1-1 sh -c 'echo 0x7e > /proc/6160/coredump_filter'
and on target, coredump_filter is zero.
$ cat /proc/6160/coredump_filter
00000000
However, I remove "sh -c", like:
$ /usr/bin/ssh -l yaoqi01 linaro-junor1-1 'echo 0x7e >
/proc/6160/coredump_filter'
then the coredump_filter is correctly set,
$ cat /proc/6160/coredump_filter
0000007e
--
You are receiving this mail because:
You are on the CC list for the bug.