On Wed, 01 Dec 1999, you wrote:
> On Wed, 01 Dec 1999, you wrote:
> > >I am having a problem getting gdb with palm patches to compile on my RH6.1
> > >system. Is there a mailing list for palm development on unix?
> > I had a similar problem. As far as I could work out there was a bad
> > function prototype for strdup,
> > 
> >     gdb_string.h: char * strdup();
> > 
> > Where as on a standard redhat I think the standard definition of strdup is
> > something along the lines of,
> > 
> >     char * strdup(const char *);
> > 
> > 
> > Also remember to tell the compiler to target palmos, this is easy to miss.
> > It should be able to pick up the host ok, although it failed to pick out
> > anything as specific as RedHat. RedHat is somewhat proprietary in terms of
> > where it puts stuff maybe thats why it got confused about strdup.
> > 
> > I ran configure as follows:
> >     ./configure --target=m68k-palmos-coff
> > 
> > Anyway I got it to compile and run but it still dumps the core as soon as I
> > try and target pilot localhost:2000. The newer version of POSE let you
> > specify which port gdb talk to by editing .poserc (there is no menu option
> > for it) but I have failed to get a debug prompt yet. I am going get gdb-i386
> > and strace on the case as soon as possible. I have a sneaky suspicion that
> > there is some problem with connecting to port 2000 on my linux box (although
> > I am not aware of any service running on it). Any linux gurus out there that
> > maybe able to answer shed any light on this.
> > 
> > There is an rpm for the palmos version of gdb for those who don't want to
> > bother compiling it.
> > 
> > Haemish.
> 
> Yup, that's it. I will try to change it. 
> 
> Are you getting a dump after a memory problem? I ran into something on the
> pilot.programmer.gcc on dejanews that had the fix for that.
> 
> Derek

Here is the message. I haven't tried it yet.

Derek

>From - Wed Dec  1 16:48:33 1999
From: [EMAIL PROTECTED] (David Turnbull)
Subject: GDB and Red Hat - here is the patch
Date: Tue, 03 Mar 1998 17:24:40 GMT
Message-ID: <[EMAIL PROTECTED]>
X-Newsreader: Forte Agent 1.5/32.452
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: pilot.programmer.gcc
Lines: 36
Path: darrin2.massena.com

I spent a couple hours tracking this down and I hope it save someone
else some time.  On RedHat, if you build the prc-tools package and get
an error running gdb you can fix it with this patch.

Unfortunately prc-tools make files don't make this patch easy.  How
you choose to make this work is up to you.  I can think of at least 6
ways to do this, none of which are elegant enough to document.

-david

--- gdb-4.16/gdb/Makefile.in.ewt        Tue Aug 19 12:08:58 1997
+++ gdb-4.16/gdb/Makefile.in    Tue Aug 19 12:15:52 1997
@@ -90,14 +90,14 @@
 # Where is the MMALLOC library?  Typically in ../mmalloc.
 # Note that mmalloc can still be used on systems without mmap().
 # To use your system malloc, comment out the following defines.
-MMALLOC_DIR = ../mmalloc
-MMALLOC_SRC = $(srcdir)/$(MMALLOC_DIR)
-MMALLOC = $(MMALLOC_DIR)/libmmalloc.a
+#MMALLOC_DIR = ../mmalloc
+#MMALLOC_SRC = $(srcdir)/$(MMALLOC_DIR)
+#MMALLOC = $(MMALLOC_DIR)/libmmalloc.a
 # To use your system malloc, uncomment MMALLOC_DISABLE.
-#MMALLOC_DISABLE = -DNO_MMALLOC
+MMALLOC_DISABLE = -DNO_MMALLOC
 # To use mmalloc but disable corruption checking, uncomment
MMALLOC_CHECK
 #MMALLOC_CHECK = -DNO_MMALLOC_CHECK
-MMALLOC_CFLAGS = -I$(MMALLOC_SRC) $(MMALLOC_CHECK) $(MMALLOC_DISABLE)
+MMALLOC_CFLAGS = $(MMALLOC_CHECK) $(MMALLOC_DISABLE)
 
 # Where is the BFD library?  Typically in ../bfd.
 BFD_DIR = ../bfd

Reply via email to