This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
mi-var-child failures
- From: Vladimir Prus <vladimir at codesourcery dot com>
- To: gdb at sources dot redhat dot com
- Cc: Nick Roberts <nickrob at snap dot net dot nz>
- Date: Tue, 15 Jan 2008 19:50:26 +0300
- Subject: mi-var-child failures
Nick,
it seems like your recent patch for 'noneditable' attribute
makes some tests to be non-deterministic. Specifically, we
get those failures on embedded targets:
-PASS: gdb.mi/mi2-var-child.exp: is weird.int_ptr_ptr.*int_ptr_ptr editable
-PASS: gdb.mi/mi2-var-child.exp: is weird.int_ptr_ptr.*int_ptr_ptr.**int_ptr_ptr editable
+FAIL: gdb.mi/mi2-var-child.exp: is weird.int_ptr_ptr.*int_ptr_ptr editable
+FAIL: gdb.mi/mi2-var-child.exp: is weird.int_ptr_ptr.*int_ptr_ptr.**int_ptr_ptr editable
What's happening here is that we have pointer initialized to NULL, and
create a varobj for the dereferenced pointer, and get its attributes.
Now, on Linux we can't dereference NULL pointer, so that value stored in
varobj ends up being NULL, and we return the value is not editable.
On embedded system, you might be allowed to access NULL pointer, and in
that case varobj is editable.
This is not a problem with GDB -- it's acting right, so FAIL on embedded target
is not indicative of a problem. I think we get to fix the testcase itself.
Mind if I make the pointer point to valid memory on all systems?
- Volodya