This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [RFA]: Modified Watchthreads Patch

From: "Eli Zaretskii" <eliz at gnu dot org>
To: Michael Snyder <msnyder at redhat dot com>
Cc: jjohnstn at redhat dot com, gdb-patches at sources dot redhat dot com
Date: Fri, 24 Dec 2004 13:03:29 +0200
Subject: Re: [RFA]: Modified Watchthreads Patch
References: <41B8E16D.6070505@redhat.com> <01c4deb2$Blat.v2.2.2$ce83b6e0@zahav.net.il> <41CB471E.8060500@redhat.com>
Reply-to: Eli Zaretskii <eliz at gnu dot org>

> Date: Thu, 23 Dec 2004 14:30:54 -0800
> From: Michael Snyder <msnyder@redhat.com>
> CC: Jeff Johnston <jjohnstn@redhat.com>, gdb-patches@sources.redhat.com
> 
> Good grief -- they all get coff, dwarf, elf, stabs, and mdebug 
> readers... what's a function here or there?   ;-)

Not all the readers are just ballast.  For example, the DJGPP
development tools support 3 debug formats: COFF, stabs, and DWARF2,
and 2 executable formats: COFF and stubbed COFF.

And I do think we should have some machinery in place to determine at
configure time what readers will be compiled in.

References:
- [RFA]: Modified Watchthreads Patch
  - From: Jeff Johnston
- Re: [RFA]: Modified Watchthreads Patch
  - From: Eli Zaretskii
- Re: [RFA]: Modified Watchthreads Patch
  - From: Michael Snyder

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]