This is the mail archive of the gdb-patches@sourceware.cygnus.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]

Re: GDB 5.0 2000-03-05

To: hjl at lucon dot org
Subject: Re: GDB 5.0 2000-03-05
From: Mark Kettenis <kettenis at wins dot uva dot nl>
Date: Wed, 8 Mar 2000 01:49:10 +0100
CC: kingdon at redhat dot com, msnyder at cygnus dot com, gdb-patches at sourceware dot cygnus dot com
References: <38C2320A.E2134B29@cygnus.com> <20000305094341.A10426@lucon.org> <br9dojaan.fsf@rtl.cygnus.com> <20000306094553.B28105@lucon.org> <200003061753.MAA14567@devserv.devel.redhat.com> <20000307161242.A485@lucon.org>

   Date: Tue, 7 Mar 2000 16:12:42 -0800
   From: "H . J . Lu" <hjl@lucon.org>

   This patch disable the thread_db interface by default. gdb works MUCH
   better now with threaded programs, including the testcase above. May
   I suggest for 5.0, we disable thread_db and fix whatever bugs we can
   fix in linux-thread.c? I will take a closer look at linux-thread.c
   when I find time.

   Thanks.

I like this approach.  Then we can simply enable thread_db when we've
fixed all critical bugs.

But the patch looks wrong to me.  Seems to *enable* thread_db by
default, end what's up with LIN_CTHREAD_CFLAGS?

Mark

Follow-Ups:
- Re: GDB 5.0 2000-03-05
  - From: H . J . Lu
- Re: GDB 5.0 2000-03-05
  - From: Jim Kingdon

References:
- GDB 5.0 2000-03-05
  - From: Andrew Cagney
- Re: GDB 5.0 2000-03-05
  - From: H . J . Lu
- Re: GDB 5.0 2000-03-05
  - From: Jim Kingdon
- Re: GDB 5.0 2000-03-05
  - From: H . J . Lu
- Re: GDB 5.0 2000-03-05
  - From: Jim Kingdon
- Re: GDB 5.0 2000-03-05
  - From: H . J . Lu

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