Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "H . J . Lu" <hjl@lucon.org>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Mark Kettenis <kettenis@wins.uva.nl>,
	jtc@redback.com, shebs@apple.com, gdb@sourceware.cygnus.com
Subject: Re: A patch for gnu-regex
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <20000309153922.A8624@lucon.org> (raw)
In-Reply-To: <38C82D34.31E36610@cygnus.com>

On Fri, Mar 10, 2000 at 10:01:08AM +1100, Andrew Cagney wrote:
> 
> I would like to see GDB-5 provide consistent behavour across all the
> random GNU/Linux distributions that are out there.  I think this is
> consistent with other applications that rely on regexp - VI being a very
> very good example.  I also want to be able to say, with some certainty,
> that a users regexp problem is attributable to GDB and _not_ random
> regexp of the day.

It seems that gdb is the only program you care on a GNU/Linux system.
You don't care if glibc nor other system programs work correctly or
not. As a long time Linux C library developer, I have received so
many bug reports derived from the system programs. I don't see
many Linux people go out to get their own replacements for the broken
functions in libc. I guess that is the one difference between Linux
and GNU. We are not writing replacements. We are working on the system
default.

> 
> A GNU/Linux distributor is free to build a GDB that regexp from an
> installed glibc. Actually such a distributor is free to do what ever
> they like :-)

Are you saying as far as gdb is concerned, you have no interests
whatsoever in glibc nor helping glibc developers and GNU/Linux
distributors? If it is true, that is too bad.


H.J.
From grante@visi.com Sat Apr 01 00:00:00 2000
From: Grant Edwards <grante@visi.com>
To: gdb@sourceware.cygnus.com
Subject: RDI target broken in 000215 snapshot
Date: Sat, 01 Apr 2000 00:00:00 -0000
Message-id: <20000221104541.A28578@visi.com>
X-SW-Source: 2000-q1/msg00361.html
Content-length: 746

The RDI target support seems to be broken in the 000215
snapshot.  I'm unable to execute any of the eCos test programs,
or any other applictions I've written. (they run fine with a
patched-up 4.18 gdb).  I don't know what's wrong with it and
won't have time to look at it for a while.  

Is somebody currently working on the RDI code?  If so, I'll
leave well enough alone until the code stabilizes.

[I've gotten fed up with the RDI code that only lets you use
certain devices for the serial connection to the target (and
the one I have connected is never one of the allowed devices),
so I decided to fix the code to allow the user to specify any
device he wants.  For now I guess I'll work with 4.18 sources.]

-- 
Grant Edwards
grante@visi.com
From ac131313@cygnus.com Sat Apr 01 00:00:00 2000
From: Andrew Cagney <ac131313@cygnus.com>
To: Eli Zaretskii <eliz@delorie.com>
Cc: gdb@sourceware.cygnus.com
Subject: Re: annotate.texi
Date: Sat, 01 Apr 2000 00:00:00 -0000
Message-id: <38C74298.B562FDD1@cygnus.com>
References: <200003070832.DAA14451@indy.delorie.com>
X-SW-Source: 2000-q1/msg00633.html
Content-length: 589

Eli Zaretskii wrote:
> 
> Is there any reason why annotate.texi shouldn't be @include'd by
> gdb.texinfo and be part of the manual?  Right now, "set annotate" is
> not documented at all, and annotate.texi seems to be just what the
> doctor ordered...

I just wonder if we want to encourage its use :-)

> And while at that, NEWS seems to be in the need of some work, it
> doesn't mention many of the new features that already are in the CVS
> tree.  I would like at least to mention the improvements in the DJGPP
> version.

A call for news is on my list of pre 5.0 things-to-do.

	Andrew
From rearnsha@arm.com Sat Apr 01 00:00:00 2000
From: Richard Earnshaw <rearnsha@arm.com>
To: Grant Edwards <grante@visi.com>
Cc: rearnsha@arm.com
Subject: Re: Address of variable doesn't work (ARM-ELF 4.18)? 
Date: Sat, 01 Apr 2000 00:00:00 -0000
Message-id: <200001271540.PAA27230@cam-mail2.cambridge.arm.com>
References: <20000126103232.A15413@visi.com>
X-SW-Source: 2000-q1/msg00061.html
Content-length: 689

grante@visi.com said:
> Using arm-elf-gdb 4.18, how do I get gdb to print the address of a
> variable or to use the address of a variable as the argument for an
> 'x' command? 

Info address should give you what you want, and a lot more besides.  It 
works even if the symbol you have asked for is in a register.

(gdb) info address main
Symbol "main" is a function at address 0x3b064.

(gdb) info address optimize
Symbol "optimize" is static storage at address 0x3214d4.

(gdb) info address argc
Symbol "argc" is an argument at offset 68.

(gdb) info address p
Symbol "p" is a local variable at frame offset -20.

(gdb) info address c
Symbol "c" is a variable in register l0.


Richard.


  reply	other threads:[~2000-04-01  0:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <38C585BB.3F7B1AC7@apple.com>
     [not found] ` <20000307155806.A30106@valinux.com>
     [not found]   ` <5mg0u2l3g0.fsf@jtc.redbacknetworks.com>
     [not found]     ` <20000307162127.D485@lucon.org>
     [not found]       ` <200003080044.e280iGB00429@delius.kettenis.local>
     [not found]         ` <5m4saivyew.fsf@jtc.redbacknetworks.com>
2000-04-01  0:00           ` Andrew Cagney
2000-04-01  0:00             ` H . J . Lu [this message]
     [not found]           ` <20000307211842.C1573@lucon.org>
     [not found]             ` <5mvh2yugpy.fsf@jtc.redbacknetworks.com>
     [not found]               ` <20000308091030.B3150@lucon.org>
     [not found]                 ` <200003081758.SAA17064@landau.wins.uva.nl>
2000-04-01  0:00                   ` H . J . Lu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20000309153922.A8624@lucon.org \
    --to=hjl@lucon.org \
    --cc=ac131313@cygnus.com \
    --cc=gdb@sourceware.cygnus.com \
    --cc=jtc@redback.com \
    --cc=kettenis@wins.uva.nl \
    --cc=shebs@apple.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox