Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@wins.uva.nl>
To: dan@cgsoftware.com
Cc: hjl@lucon.org, gdb@sourceware.cygnus.com
Subject: Re: Preparing for the GDB 5.0 / GDB 2000 / GDB2k release
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <200002080051.e180pit26400@delius.kettenis.local> (raw)
In-Reply-To: <Pine.LNX.4.10.10002071633590.9778-100000@propylaea.anduin.com>

   Date: Mon, 7 Feb 2000 16:35:27 -0800 (PST)
   From: Daniel Berlin <dan@cgsoftware.com>

   > Debugging shared libraries works most of time with gdb 4.17.0.14.
   > If it doesn't work with 5.0, does that count for serious losses of
   > functionality? I believe many people will be very disappointed
   > if it doesn't unless we can fix it within 2 months.

   You mean for your particular architecture.
   Please don't forget that.
   Debugging shared libs works perfectly fine under BeOS, with my beos port,
   using nothing but the standard solib hooks.

I bet debugging apps that dlopen() a shared object, then dlclose() it
and then dlopen() a different shared object won't work under BeOS
either (if that is possible under BeOS at all), but other than that,
I'm not aware of any deficiencies.

HJ, are you really aware of problems with debugging shared objects
that don't involve a dlclose() somehow?  If you are, could you *please*
provide a testcase.

Mark



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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.10.10002071633590.9778-100000@propylaea.anduin.com>
2000-04-01  0:00 ` Mark Kettenis [this message]
2000-04-01  0:00 Kevin_Hendricks
     [not found] <389ECBAF.66013B07@cygnus.com>
     [not found] ` <200002071626.RAA18391@landau.wins.uva.nl>
     [not found]   ` <bog9tj5y3.fsf@rtl.cygnus.com>
2000-04-01  0:00     ` Mark Kettenis
     [not found]     ` <20000207093417.A10546@lucon.org>
     [not found]       ` <200002071746.MAA22221@devserv.devel.redhat.com>
     [not found]         ` <20000207095901.A10677@lucon.org>
2000-04-01  0:00           ` Andrew Cagney
2000-04-01  0:00             ` Patrick J. LoPresti
     [not found] <389EC815.BC34F3E6@cygnus.com>
2000-04-01  0:00 ` Jason Molenda
     [not found] <20000207174307.B12317@lucon.org>
2000-04-01  0:00 ` Daniel Berlin
     [not found] <200002082018.MAA12871@propylaea.anduin.com>
2000-04-01  0:00 ` Daniel Berlin

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=200002080051.e180pit26400@delius.kettenis.local \
    --to=kettenis@wins.uva.nl \
    --cc=dan@cgsoftware.com \
    --cc=gdb@sourceware.cygnus.com \
    --cc=hjl@lucon.org \
    /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