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
