[ircd-ratbox] AMD64.

'Tim Jensen' tim at timandkibbie.com
Fri Jun 4 09:31:56 EDT 2004


gdb6 should build successfully.  /usr/ports/devel/gdb6/Makefile
seems to indicate it will build for AMD64, but if not, you should be
able to build it straight from a 6.x snapshot tarball:
	http://tinyurl.com/2je44

Tim

On Thu, Jun 03, 2004 at 10:12:13PM -0400, Paul-Andrew Joseph Miseiko wrote:
> 4:10am esoteric at anduin-ttypc [/usr/ports/devel/gdb53] make
> ===>  gdb-5.3_1,1 is marked as broken: Configure fails on amd64.
> 4:10am esoteric at anduin-ttypc [/usr/ports/devel/gdb53] cd ../gdb52
> 4:10am esoteric at anduin-ttypc [/usr/ports/devel/gdb52] make
> ===>  gdb-5.2.1_2 is marked as broken: Configure fails on amd64.
> 
> Any known good alternatives?
> 
> -----Original Message-----
> From: Tim Jensen [mailto:tim at timandkibbie.com] 
> Sent: June 3, 2004 9:46 AM
> To: Paul-Andrew Joseph Miseiko
> Cc: ircd-ratbox at lists.ratbox.org
> Subject: Re: [ircd-ratbox] AMD64.
> 
> I have access to AMD64 hardware and can try to reproduce the problem
> you have described.  What version of FreeBSD are you using?
> 
> I'm quite surprised to hear GDB doesn't compile on FreeBSD/AMD64,
> considering its Tier-1 status.  Have you tried building any of the GDB
> versions in /usr/ports?
> 
> Tim
> 
> 
> On Thu, Jun 03, 2004 at 08:36:43AM -0400, Paul-Andrew Joseph Miseiko wrote:
> > It's funny how everybody that responded to my original email state they
> have
> > this hardware or that hardware but nobody had the appropriate hardware to
> > actually provide relevant information.  Thanks anyway.
> > 
> > The old dual Intel system has reacquired the act of providing IRC services
> > where the AMD 64bit system could not.  So at this time I do not need any
> > more information, however in the interests of future development I would
> be
> > willing to grant shell access to any member of the RATBOX development team
> > on the AMD 64bit system in question.
> > 
> > Quick points; "gdb" does not compile on AMD 64bit.  There is no "truss" or
> > "strace".  I am unaware of any other methods for debugging programs other
> > then good old fashion printf() statements.
> > 
> > Something like,
> > #define return printf( "%s:%u return\n", __FILE__, __LINE__ ); return
> > 
> > I might try it myself if I get some time in the near future.
> > 
> > -----Original Message-----
> > From: Dustin Marquess [mailto:jailbird at alcatraz.fdf.net] 
> > Sent: June 3, 2004 12:29 AM
> > To: Aaron Sethman
> > Cc: Paul-Andrew Joseph Miseiko; ircd-ratbox at lists.ratbox.org
> > Subject: Re: [ircd-ratbox] AMD64.
> > 
> > My main ircd box is a 500Mhz 21164A EV56 Alpha, running Tru64.  I haven't
> > had
> > any of these problems on there.  I also have a Sun Ultra Enterprise 2
> > running
> > a sparc64 2.6.5 Linux kernel.  I haven't done a lot of testing on the
> sparc,
> > but I haven't seen anything noticable.
> > 
> > -Dustin
> > 
> > Aaron Sethman <androsyn at ratbox.org> wrote:
> > > 
> > > On Sun, 30 May 2004, Paul-Andrew Joseph Miseiko wrote:
> > > 
> > > > Are there any known issues with AMD 64 compatibility on FreeBSD
> compiled
> > for
> > > > true 64bit support.  The IRCD has a tendency to core dump (SIGSEGV)
> when
> > > > clients connect to it.  Unfortunately gdb did not seem to compile with
> > the
> > > > world leaving me with no stack trace but a core dump does exist if
> > anybody
> > > > wants a peek.
> > > 
> > > There aren't any that I know of, but I've not tested on AMD64 on FreeBSD
> > > either.  I do know that ircd-ratbox does work okay on sparc64 on Linux
> and
> > > Solaris.  If you could get a useful gdb to debug these, would be helpful
> > > of course.
> > 
> > _______________________________________________
> > ircd-ratbox mailing list
> > ircd-ratbox at lists.ratbox.org
> > http://lists.ratbox.org/cgi-bin/mailman/listinfo/ircd-ratbox
> 
> -- 
> Tim Jensen
> 0x39E9AF2D
> 

-- 
Tim Jensen
0x39E9AF2D


More information about the ircd-ratbox mailing list