Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@delorie.com>
To: kingdon@redhat.com
Cc: gdb@sourceware.cygnus.com
Subject: Re: Dependence on config.status
Date: Fri, 03 Mar 2000 22:53:00 -0000	[thread overview]
Message-ID: <200003040653.BAA08138@indy.delorie.com> (raw)
In-Reply-To: <bem9u49sh.fsf@rtl.cygnus.com>

The following changes remove the dependency of GDB on config.status.

If people would still like to have automatic recompile when [ntx]m.h
are linked to different files, I think the correct way is to make
configure define [NTX]M_FILE symbols on config.h by using the values
of ${nativefile}, ${targetfile}, and ${hostfile}, which it already
computes.


2000-03-03  Eli Zaretskii  <eliz@is.elta.co.il>

	gdb/Makefile.in (defs_h): Don't depend on config.status.  (This
	is only needed when [ntx]m.h headers are linked to another set
	of files, in which case they should "make clean".)

--- gdb/Makefile.i~0	Tue Feb 22 10:52:06 2000
+++ gdb/Makefile.in	Fri Mar  3 13:52:30 2000
@@ -495,7 +496,7 @@
 gdbcmd_h =	gdbcmd.h $(command_h)
 
 call_cmds_h =	call-cmds.h
-defs_h =	defs.h xm.h tm.h nm.h config.status config.h gdbarch.h ui-file.h
+defs_h =	defs.h xm.h tm.h nm.h config.h gdbarch.h ui-file.h
 
 top_h =		top.h
 inferior_h =	inferior.h $(breakpoint_h)
From eliz@delorie.com Fri Mar 03 23:03:00 2000
From: Eli Zaretskii <eliz@delorie.com>
To: muller@cerbere.u-strasbg.fr
Cc: kettenis@wins.uva.nl, gdb@sourceware.cygnus.com
Subject: Re: RFD: New command to inspect other selectors memory.
Date: Fri, 03 Mar 2000 23:03:00 -0000
Message-id: <200003040703.CAA08165@indy.delorie.com>
References: <200003021432.PAA01976@cerbere.u-strasbg.fr> <200003021347.OAA01051@cerbere.u-strasbg.fr> <200003021257.NAA00259@cerbere.u-strasbg.fr> <200003030843.JAA12246@cerbere.u-strasbg.fr>
X-SW-Source: 2000-03/msg00070.html
Content-length: 592

> I have written for DJGPP target a relatively small patch.
> It allows to read memory from another selector
> this was very useful for me when I tried to debug the debugger itself and 
> when I added exception support fro GDB on DJGPP !

I have this patch on my disk, and will review it when I have time.

>   Is such kind of patch too specific to have any chance to get accepted ?
> I don't know if it could be of any use for other processors or operating
> system !!

I second the question.

In any case, I understand that there's no problem to add architecture-
specific commands, right?
From eliz@delorie.com Fri Mar 03 23:04:00 2000
From: Eli Zaretskii <eliz@delorie.com>
To: kettenis@wins.uva.nl
Cc: muller@cerbere.u-strasbg.fr, gdb@sourceware.cygnus.com
Subject: Re: RFD: New command to inspect other selectors memory.
Date: Fri, 03 Mar 2000 23:04:00 -0000
Message-id: <200003040704.CAA08168@indy.delorie.com>
References: <200003021432.PAA01976@cerbere.u-strasbg.fr> <200003021347.OAA01051@cerbere.u-strasbg.fr> <200003021257.NAA00259@cerbere.u-strasbg.fr> <200003030843.JAA12246@cerbere.u-strasbg.fr> <200003031240.e23CeRn00162@delius.kettenis.local>
X-SW-Source: 2000-03/msg00071.html
Content-length: 170

> The suggested syntax could probably be
> improved, since "xx" isn't very descriptive.  People with bright ideas?

How about "x/seg=SEG OFFSET"?  Or simply "x SEG:OFF"?
From eliz@delorie.com Fri Mar 03 23:07:00 2000
From: Eli Zaretskii <eliz@delorie.com>
To: ac131313@cygnus.com
Cc: muller@cerbere.u-strasbg.fr, kettenis@wins.uva.nl, gdb@sourceware.cygnus.com
Subject: Re: RFD: New command to inspect other selectors memory.
Date: Fri, 03 Mar 2000 23:07:00 -0000
Message-id: <200003040706.CAA08171@indy.delorie.com>
References: <200003021432.PAA01976@cerbere.u-strasbg.fr> <200003021347.OAA01051@cerbere.u-strasbg.fr> <200003021257.NAA00259@cerbere.u-strasbg.fr> <200003030843.JAA12246@cerbere.u-strasbg.fr> <38BFB50A.606036CF@cygnus.com>
X-SW-Source: 2000-03/msg00072.html
Content-length: 232

> The theory is that if ``CORE_ADDR'' is made in to a pretend object
> (ISO-C remember :-) and then the rest falls out....  As they say, the
> proof is left as an exercise to the reader.

Sorry, I don't follow.  Can you elaborate?


       reply	other threads:[~2000-03-03 22:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200002280657.BAA27090@indy.delorie.com>
     [not found] ` <38BCCA84.74A4143E@cygnus.com>
     [not found]   ` <bem9u49sh.fsf@rtl.cygnus.com>
2000-03-03 22:53     ` Eli Zaretskii [this message]
     [not found]     ` <200003021007.FAA04124@indy.delorie.com>
2000-03-03 23:08       ` Andrew Cagney

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=200003040653.BAA08138@indy.delorie.com \
    --to=eliz@delorie.com \
    --cc=gdb@sourceware.cygnus.com \
    --cc=kingdon@redhat.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