Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Doug Evans" <dje@google.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFA] new command to search memory
Date: Fri, 09 May 2008 06:35:00 -0000	[thread overview]
Message-ID: <e394668d0805081951rf692bf3xed8e8062d7de370b@mail.gmail.com> (raw)
In-Reply-To: <20080502151742.GM29202@caradoc.them.org>

On Fri, May 2, 2008 at 8:17 AM, Daniel Jacobowitz <drow@false.org> wrote:
>> Index: gdbserver/Makefile.in
>> ===================================================================
>> RCS file: /cvs/src/src/gdb/gdbserver/Makefile.in,v
>> retrieving revision 1.57
>> diff -u -p -u -p -r1.57 Makefile.in
>> --- gdbserver/Makefile.in     14 Apr 2008 18:04:00 -0000      1.57
>> +++ gdbserver/Makefile.in     17 Apr 2008 02:35:24 -0000
>> @@ -81,11 +81,15 @@ BFD_CFLAGS = -I$(BFD_DIR) -I$(BFD_SRC)
>>  READLINE_DIR = ${srcdir}/../readline
>>  READLINE_DEP = $$(READLINE_DIR)
>>
>> +# gnulib
>> +INCGNULIB = -I$(srcdir)/../gnulib -I../gnulib
>> +
>>  # All the includes used for CFLAGS and for lint.
>>  # -I. for config files.
>>  # -I${srcdir} for our headers.
>>  # -I$(srcdir)/../regformats for regdef.h.
>> -INCLUDE_CFLAGS = -I. -I${srcdir} -I$(srcdir)/../regformats -I$(INCLUDE_DIR)
>> +INCLUDE_CFLAGS = -I. -I${srcdir} -I$(srcdir)/../regformats -I$(INCLUDE_DIR) \
>> +     $(INCGNULIB)
>>
>>  # M{H,T}_CFLAGS, if defined, has host- and target-dependent CFLAGS
>>  # from the config/ directory.
>> @@ -143,7 +147,7 @@ TAGFILES = $(SOURCES) ${HFILES} ${ALLPAR
>>
>>  OBS = inferiors.o regcache.o remote-utils.o server.o signals.o target.o \
>>       utils.o version.o \
>> -     mem-break.o hostio.o \
>> +     mem-break.o memmem.o hostio.o \
>>       $(XML_BUILTIN) \
>>       $(DEPFILES) $(LIBOBJS)
>>  GDBSERVER_LIBS = @GDBSERVER_LIBS@
>
> The gdbserver configure script should already be taking care of all
> these.  In particular we don't want to reference ../gnulib in the
> objdir since it won't exist if you're just building gdbserver.  And I
> know it will add memmem.o, I tested that.

I thought gnulib/memmem.o was always going to be used.   We started
down this path because, in part, libc's memmem is O(n^2).

configure ...
checking for memmem... yes

after making gdbserver ...
$ nm gdbserver | grep memmem
         U memmem@@GLIBC_2.0

> Does that leave just the declaration?  You can stick it somewhere in
> gdbserver instead of bringing in all the replacement gnulib headers.


  reply	other threads:[~2008-05-09  2:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-14  2:20 Doug Evans
2008-02-14 19:54 ` Eli Zaretskii
2008-02-14 22:52   ` Doug Evans
2008-02-15  8:28     ` Eli Zaretskii
2008-02-16  5:39       ` Doug Evans
2008-02-16 13:33         ` Eli Zaretskii
2008-02-26  2:31 ` Daniel Jacobowitz
2008-02-29  3:13   ` Doug Evans
2008-02-29  3:58     ` Daniel Jacobowitz
2008-04-17  2:59       ` Doug Evans
2008-04-28 18:37         ` Fwd: " Doug Evans
2008-04-29  0:40           ` Eli Zaretskii
2008-05-09  6:46             ` Doug Evans
2008-05-09 14:35               ` Eli Zaretskii
2008-05-02 15:19         ` Daniel Jacobowitz
2008-05-09  6:35           ` Doug Evans [this message]
2008-05-09  7:33             ` Daniel Jacobowitz
2008-05-09 20:16           ` Doug Evans
2008-05-09 20:18             ` Daniel Jacobowitz
2008-04-09 21:06   ` Doug Evans
2008-05-02 15:37     ` Daniel Jacobowitz

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=e394668d0805081951rf692bf3xed8e8062d7de370b@mail.gmail.com \
    --to=dje@google.com \
    --cc=gdb-patches@sourceware.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