Bug 8651 - corrupt stack?
Summary: corrupt stack?
Status: RESOLVED DUPLICATE of bug 8652
Alias: None
Product: gdb
Classification: Unclassified
Component: backtrace (show other bugs)
Version: 6.0
: P3 normal
Target Milestone: ---
Assignee: Michael Elizabeth Chastain
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-09 10:08 UTC by nik
Modified: 2008-12-19 19:15 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description nik 2004-02-09 10:08:00 UTC
[Converted from Gnats 1546]

Server receives SIGSEGV, program stops. But when I called 'bt', GDB 5.3 shows me frames without any symbol table information (only address), 6.0 says: "Previous frame inner to this frame (corrupt stack?)". GDB typescripts are in attachments. It repeats very often, I don't know what to do. Error happens cause 'tmp' is 'char tmp[30]', but 'i' is aproximatly 62438. But how to fix if stack is "corrupted"? Is this a bug or maybe it has another explanation?..

Release:
5.3 & 6.0 also

Environment:
Red Hat Linux release 6.2 (Zoot). Kernel 2.2.14-5.0 on an i686.

How-To-Repeat:
Get chessd called lasker (v.2.2.2.) from http://chess.samba.org/, enter as guests, create match by command "match guest_nick 20 150 black", and make first move - 'd2d3'. Thats all.
Comment 1 Michael Elizabeth Chastain 2004-02-09 17:30:25 UTC
*** This bug has been marked as a duplicate of 8652 ***