This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: adjust linux-dp test
On Wed, Nov 29, 2006 at 03:14:50PM +0000, Nathan Sidwell wrote:
> Daniel Jacobowitz wrote:
> >On Wed, Nov 29, 2006 at 02:58:08PM +0000, Nathan Sidwell wrote:
> >>My recent change to linux-dp.exp wasn't robust because (a) some thread
> >>ids can be negative numbers and (b) sometimes you'd get a 'cannot access
> >>memory' error in printing out a prototype, and that would mess up the \n
> >>placement.
> >
> >When does (b) happen? That's strange.
>
> for example here ...
> info threads
> 3 Thread -1218434144 (LWP 2749) 0xffffe410 in __kernel_vsyscall ()
> 2 Thread -1210037344 (LWP 2748) 0xffffe410 in __kernel_vsyscall ()
> * 1 Thread -1210034512 (LWP 2745) main (argc=Cannot access memory at
> address 0x0
> ) at ../../../src/gdb/testsuite/gdb.threads/linux-dp.c:189
Well that's totally lame. I don't see how it happens, either, I'd
expect the error in val_print to catch it.
I think you need to allow newlines in this output anyway; it might wrap
printing many parameters of a function. So may as well just relax the
error for now.
--
Daniel Jacobowitz
CodeSourcery