Re: Hardware watchpoints

[Jim Blandy <jimb@cygnus.com>]

> > One question that I still can't figure out is why does GDB at all
> > _need_ to have the parent struct on the value chain?  Where is that
> > information used?
> 
> GDB doesn't *need* it, per se.

Sorry --- there's a better answer to that question.

In evaluating the expression x.y, the value chain will contain a value
for the entire structure x, and a value for the member, x.y.  The
former value is needed by the '.' operator; the operator extracts the
'y' member from it.
From toddpw@windriver.com Sun Oct 24 22:10:00 1999
From: Todd Whitesel <toddpw@windriver.com>
To: ogoh@cise.ufl.edu (Okehee Goh)
Cc: gdb@sourceware.cygnus.com (GDB Developers)
Subject: Re: [GDB] Can I get some sample program using debugging stub?
Date: Sun, 24 Oct 1999 22:10:00 -0000
Message-id: <199910250510.WAA09745@alabama.wrs.com>
References: <000e01bf1dd6$3b355120$8daae380@oriole.hsi-lab.cise.ufl.edu>
X-SW-Source: 1999-q4/msg00158.html
Content-length: 1333

> According to GDB manual, they said , "Insert set_debug_traps, breakpoint
> near the top of your program". But It's not concrete to me.

Pick a function like 'main' or 'myApp' or whatever you call your functions
that begin the program; and set a breakpoint there:

(gdb) break main

> I compiled GDB for "--target=sparc-wrs-vxworks" as target and solraris2 as

If you are using a public version of GDB, then this requires an older vxworks
target that supports 'RDB'. Newer targets (those shipped with Tornado 2.0) do
not support RDB any more.

I am working to get something appropriate for T2.0 into the public GDB but it
is slow going as I missed my best window of opportunity last winter by getting
really sick at just the wrong time.

> When tried to debug the application compiled under solaris2, it failed to
> read the file format. I guess the gdb which is made for cross debugging for
> another architecture can't work for the application of host that GDB works.
> Am I right?

That is generally true. If you build a program with gcc for a --target, then
you will also need a gdb for the same --target in order to debug it. If you
want to debug programs compiled by the solaris2 compiler, you should use a gdb
for --target=sparc-sun-solaris2.5.1 (or whatever version of solaris you have).

-- 
Todd Whitesel
toddpw @ wrs.com
From rearnsha@arm.com Mon Oct 25 03:26:00 1999
From: Richard Earnshaw <rearnsha@arm.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: richard.earnshaw@arm.com
Subject: Re: wrong htons() used? 
Date: Mon, 25 Oct 1999 03:26:00 -0000
Message-id: <199910251026.LAA20361@cam-mail1.cambridge.arm.com>
References: <3813A9AC.D896D4BD@cygnus.com>
X-SW-Source: 1999-q4/msg00159.html
Content-length: 470

> More seriously, why is <netinet/in.h> picking up the wrong endian.h? 
> Has this always happened or has something else recently changed?

Probably because it goes 

#include <endian.h> 

and is then compiled with a -I somewhere_with_a_different_endian.h

If I understand gcc's include searching rules properly, netinet/in.h 
should probably go

#include "../endian.h"

so that it will start the search will start from netinet rather than using 
the include path.

R.