Re: Inetutils FTP client and GCC4

2005-08-24 Thread William Harrington
There were previous patches flying around attempting to change cmdtab[] to *cmdtab which cause cmdtab->c_name and cmdtab->c_help to automatically be out of bounds when ftp started. That way breaks it for any version of gcc cause it isn't the proper way to do it with cmdtab structure. The correct

Re: Inetutils FTP client and GCC4

2005-08-07 Thread Greg Schafer
Randy McMurchy wrote: > Some weird activity with the Inetutils FTP client when compiled with > GCC-4.0.1. Note that a new patch has been introduced to the GCC-4 > branch of LFS to "correct" GCC4 problems. This patch affects two > files used to compile the ftp client program. If anybody can > expla

Re: Inetutils FTP client and GCC4

2005-08-07 Thread William Harrington
On Sun, 07 Aug 2005 15:46:56 -0500, Randy McMurchy wrote: > Hi all, > > Some weird activity with the Inetutils FTP client when compiled with > GCC-4.0.1. Note that a new patch has been introduced to the GCC-4 > branch of LFS to "correct" GCC4 problems. This patch affects two > files used to compi

RE: Inetutils FTP client and GCC4

2005-08-07 Thread David Fix
Hm... I may have been wrong, it said that p was pointing to an invalid address too... I have NO idea why q is invalid, however. Can you do a: -These commands print c ptype c print c->c_name ptype c->c_name ? Thanks. :) (I'm compiling gcc-4.01 right now, but it's being compiled on an PII

RE: Inetutils FTP client and GCC4

2005-08-07 Thread David Fix
> Looks like 'q' is the culprit: > > (gdb) print q > $2 = 0x1 Looks like it to me too. :) I'm taking a look right now to see if I can't find the problem. :) Dave -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the a

Re: Inetutils FTP client and GCC4

2005-08-07 Thread Matthew Burgess
David Fix wrote: One of them is probably pointing somewhere it shouldn't, and that's the problem. :) Once I see these, I'll see if there's anything that I can find out. :) Looks like 'q' is the culprit: (gdb) print p $1 = 0x73550022 (gdb) print q $2 = 0x1 (gdb) print name $3 = 0x80598a0

RE: Inetutils FTP client and GCC4

2005-08-07 Thread David Fix
> Program received signal SIGSEGV, Segmentation fault. > 0x08051e47 in getcmd (name=0x80598a0 "pwd") at main.c:393 > 393 for (q = name; *q == *p++; q++) > (gdb) bt > #0 0x08051e47 in getcmd (name=0x80598a0 "pwd") at main.c:393 > #1 0x080521b8 in cmdscanner (top=1) at main.c:355 > #2 0x

Re: Inetutils FTP client and GCC4

2005-08-07 Thread Matthew Burgess
David Fix wrote: Can you provide a backtrace from GDB for this? :) I'd be happy to take a look-see. :) ftp> pwd Program received signal SIGSEGV, Segmentation fault. 0x08051e47 in getcmd (name=0x80598a0 "pwd") at main.c:393 393 for (q = name; *q == *p++; q++) (gdb) bt #0 0x08051e

RE: Inetutils FTP client and GCC4

2005-08-07 Thread David Fix
> Some weird activity with the Inetutils FTP client when compiled with > GCC-4.0.1. Note that a new patch has been introduced to the GCC-4 > branch of LFS to "correct" GCC4 problems. This patch affects two > files used to compile the ftp client program. If anybody can > explain, or care to comment

Inetutils FTP client and GCC4

2005-08-07 Thread Randy McMurchy
Hi all, Some weird activity with the Inetutils FTP client when compiled with GCC-4.0.1. Note that a new patch has been introduced to the GCC-4 branch of LFS to "correct" GCC4 problems. This patch affects two files used to compile the ftp client program. If anybody can explain, or care to comment a