This is the mail archive of the gdb-prs@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: backtrace/1547: corrupt stack?

From: chastain at sourceware dot org
To: chastain at sourceware dot org, gdb-prs at sources dot redhat dot com, nik at kemsu dot ru, nobody at sources dot redhat dot com
Date: 9 Feb 2004 10:32:59 -0000
Subject: Re: backtrace/1547: corrupt stack?
Reply-to: chastain at sourceware dot org, chastain at sourceware dot org, gdb-prs at sources dot redhat dot com, nik at kemsu dot ru, nobody at sources dot redhat dot com, gdb-gnats at sources dot redhat dot com

Synopsis: corrupt stack?

Responsible-Changed-From-To: unassigned->chastain
Responsible-Changed-By: chastain
Responsible-Changed-When: Mon Feb  9 10:32:59 2004
Responsible-Changed-Why:
    
    Mine.
    
State-Changed-From-To: open->feedback
State-Changed-By: chastain
State-Changed-When: Mon Feb  9 10:32:59 2004
State-Changed-Why:
    I need the gdb typescript that you mentioned.
    
    I tried running lasker 2.2.2 on red hat linux 8.0.
    It worked fine.  I logged in as admin, then logged in twice more as two guests, did "match guest EYWJ 20 150 black", and moved d2d3, d7d6, e2e4, e7e5.  Worked fine.
    
    I really need that typescript to see what you are talking about.

http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=1547

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]