From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Fix deadlock on looped solib list
Date: Wed, 07 Apr 2010 19:47:00 -0000 [thread overview]
Message-ID: <m3y6gzujsy.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100403092301.GA21485@host0.dyn.jankratochvil.net> (Jan Kratochvil's message of "Sat, 3 Apr 2010 11:23:01 +0200")
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
Jan> While some simple n^2 check or maximal allowed libraries list could
Jan> be more simple remembering Google was patching GDB for very large
Jan> solib lists.
I don't remember hearing about this... anybody know why this isn't
in the FSF GDB?
Jan> gdb/
Jan> 2010-04-03 Jan Kratochvil <jan.kratochvil@redhat.com>
Jan> Fix deadlock on looped list of loaded shared objects.
Jan> * arch-utils.c (core_addr_hash, core_addr_eq): New.
Jan> * arch-utils.h: Include hashtab.h.
Jan> (core_addr_hash, core_addr_eq): New prototypes.
Jan> * defs.h: Include hashtab.h.
Jan> (make_cleanup_htab_delete): New prototype.
Jan> * solib-svr4.c: Include arch-utils.h.
Jan> (svr4_current_sos): New variables lm_obstack, lm_hash, outer_chain,
Jan> initialize them, call outer_chain do_cleanups at the bottom. Move new
Jan> and old_chain initializations after a new duplicity check of LM using
Jan> new variable lm_slot.
Jan> * utils.c (do_htab_delete_cleanup, make_cleanup_htab_delete): New.
This is ok. Thanks.
Tom
next prev parent reply other threads:[~2010-04-07 19:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-03 9:23 Jan Kratochvil
2010-04-07 19:47 ` Tom Tromey [this message]
2010-04-07 22:24 ` Jan Kratochvil
2010-04-07 22:39 ` Tom Tromey
2010-04-09 15:42 ` [cancel] " Jan Kratochvil
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=m3y6gzujsy.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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