From: Kevin Buettner <kevinb@cygnus.com>
To: fnf@cygnus.com, gdb-patches@sourceware.cygnus.com
Subject: Re: [PATCH] Fix auto-solib-add bug (patch revised again)
Date: Thu, 28 Jun 2001 18:07:00 -0000 [thread overview]
Message-ID: <1010629010654.ZM12146@ocotillo.lan> (raw)
In-Reply-To: <200009192140.OAA23805@fishpond.ninemoons.com>
On Sep 19, 2:40pm, fnf@ninemoons.com wrote:
> Please review and apply this patch, or let me know how it needs to be
> fixed.
Fred,
Since your patch primarily touches solib related code, it appears that
I need to review it as one of the solib maintainers. (At the time it
was submitted, however, I was not a solib maintainer.)
Anway... I've looked over your patch and it looks okay. I do have a
question, however, regarding...
> ! solib_add (args, from_tty, (struct target_ops *) 0, INT_MAX >> 22);
What does ``INT_MAX >> 22'' represent? One of my concerns regarding
this expression is that if INT_MAX is less than 4194304, this
expression will turn out to be zero which is probably not desirable.
I have not tried to apply your patch, but it seems unlikely that it'll
still apply cleanly due to the changes which have occurred in GDB
since the time of patch submission. If you have the time and inclination,
I'd really appreciate it if you could revise it to apply cleanly against
the current GDB sources. If you don't, please let me know and I'll
do it...
Thanks,
Kevin
next prev parent reply other threads:[~2001-06-28 18:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200009192140.OAA23805@fishpond.ninemoons.com>
[not found] ` <39CFDF0C.BE95DADE@ozemail.com.au>
2000-09-25 23:10 ` Post Hook Patch, and Regcache.h Patch Eli Zaretskii
2001-06-28 15:04 ` [PATCH] Fix auto-solib-add bug (patch revised again) Andrew Cagney
2001-06-28 18:07 ` Kevin Buettner [this message]
2001-06-28 19:23 ` Fred Fish
2001-07-01 15:21 ` [PATCH] Fix auto-solib-add bug (patch revised 7/1/2001) Fred Fish
[not found] ` <fnf@www.ninemoons.com>
[not found] ` <1010702215326.ZM24300@ocotillo.lan>
2001-07-02 14:56 ` Christopher Faylor
2001-07-13 15:03 ` Elena Zannoni
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=1010629010654.ZM12146@ocotillo.lan \
--to=kevinb@cygnus.com \
--cc=fnf@cygnus.com \
--cc=gdb-patches@sourceware.cygnus.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