This is the mail archive of the mailing list for the glibc 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]

[Bug libc/1789] assert() corrupts the stack?

------- Additional Comments From decimal at us dot ibm dot com  2005-11-07 17:25 -------
I tried this testcase on Fedora Core 4 i386 running on a Pentium 4 box and I get

$ gdb a.out
GNU gdb Red Hat Linux (
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"...Using host libthread_db
library "/lib/".

(gdb) run
Starting program: /home/dwayne/glibc/bug/1789/a.out
Reading symbols from shared object read from target memory...done.
Loaded system supplied DSO at 0x49c000
a.out: t.c:4: main: Assertion `i == 0' failed.

Program received signal SIGABRT, Aborted.
0x0049c402 in __kernel_vsyscall ()

It seems to me the problem is likely to either be Ubuntu specific or a problem
with gdb. My advice is to open an Ubuntu bug at
When you do that you will want to tell them the version of glibc, gcc, and gdb
that you are using. This information is available from dpkg I believe.

I'm going to mark this bug as INVALID because there is not enough information to
demonstrate that this is a generic glibc bug.

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

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