This is the mail archive of the gdb@sourceware.org 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: gdb-gdbserver, non-stop, async - thread identifier more than only a thread id?

From: Tom Tromey <tromey at redhat dot com>
To: Petr HluzÃn <petr dot hluzin at gmail dot com>
Cc: "D. Lehne" <daniel dot lehne at amk-drives dot bg>, gdb at sourceware dot org
Date: Thu, 07 Jul 2011 08:07:59 -0600
Subject: Re: gdb-gdbserver, non-stop, async - thread identifier more than only a thread id?
References: <4E0F230A.70601@amk-drives.bg> <m3d3hnm8j6.fsf@fleche.redhat.com> <CAC=yr6BLZeHcY6Y2kPdBUCaZTj_y=RSQm_mMhwqZJyO-DG_dSQ@mail.gmail.com>

>>>>> "Petr" == Petr HluzÃn <petr.hluzin@gmail.com> writes:

Petr> I guess it would be useful to skip the first several functions which
Petr> are always there. (E.g. OS thread entry, C runtime
Petr> initialization/deinitialization, a fancy framework init/deinit
Petr> routine, and finally the function the user wanted.)

Yeah, this is one reason I think it may not be advisable to do this in
GDB.  Putting this information into GDB doesn't seem very good.

I think it is easy enough to script this.

Tom

References:
- gdb-gdbserver, non-stop, async - thread identifier more than only a thread id?
  - From: D. Lehne
- Re: gdb-gdbserver, non-stop, async - thread identifier more than only a thread id?
  - From: Tom Tromey
- Re: gdb-gdbserver, non-stop, async - thread identifier more than only a thread id?
  - From: Petr HluzÃn

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