IA-64 defect in gdb, any comments what could be the problem

IA-64 defect in gdb, any comments what could be the problem

[Kotian, Deepak]

[-- Attachment #1: Type: text/plain, Size: 307 bytes --]

Hi,

   We observed a problem on IA-64 Linux(AS 2.1) in backtrace.
   Please let us know, if there are any inputs .
   It dumps a core when doing where command.
   Problem log: problem-ia64.txt attached
   Target source file which dumps a core is : test.c

   
    
	
Thanks and Regards
Deepak

[-- Attachment #2: problem-ia64.txt --]
[-- Type: text/plain, Size: 1858 bytes --]

$gdb ./test core
GNU gdb Red Hat Linux (5.2-2)
Copyright 2002 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 "ia64-redhat-linux"...
Core was generated by `./test'.
Program terminated with signal 6, Aborted.
Reading symbols from /lib/libc.so.6.1...done.
Loaded symbols for /lib/libc.so.6.1
Reading symbols from /lib/ld-linux-ia64.so.2...done.
Loaded symbols for /lib/ld-linux-ia64.so.2
#0  0x20000000000ba322 in kill () at soinit.c:56
56      soinit.c: No such file or directory.
        in soinit.c
(gdb) where
#0  0x20000000000ba322 in kill () at soinit.c:56
#1  0x20000000000ba1d0 in raise (sig=6) at ../sysdeps/posix/raise.c:27
#2  0x20000000000bca50 in abort () at ../sysdeps/generic/abort.c:88
#3  0x4000000000000770 in func6 () 
#4  0x20000000000ba1d0 in raise (sig=3592) at ../sysdeps/posix/raise.c:27
#5  0xc000000000000204 in ?? () 
#6  0x20000000000ba1d0 in raise (sig=Cannot access memory at address 0x60000fff7ffffd50
) at ../sysdeps/posix/raise.c:27
Cannot access memory at address 0x60000fff7ffffd68
(gdb) where
#0  0x20000000000ba322 in kill () at soinit.c:56
#1  0x20000000000ba1d0 in raise (sig=6) at ../sysdeps/posix/raise.c:27
#2  0x20000000000bca50 in abort () at ../sysdeps/generic/abort.c:88
#3  0x4000000000000770 in func6 () 
#4  0x20000000000ba1d0 in raise (sig=3592) at ../sysdeps/posix/raise.c:27
#5  0xc000000000000204 in ?? () 
#6  0x20000000000ba1d0 in raise (sig=Cannot access memory at address 0x60000fff7ffffd50
) at ../sysdeps/posix/raise.c:27
#7  0x00000000 in ?? ()
Segmentation fault (core dumped)

[-- Attachment #3: test.c --]
[-- Type: application/octet-stream, Size: 433 bytes --]

#include <stdio.h>
void func7()
{
int i,j;
int *pt = NULL;
int k;
/**pt = 100;*/
i=10;
j=5;
k=i*j;
abort();
}


int func6()
{
  int i=1;
  func7();
}
int func5()
{
  int i=1;
  func6();
  i++;
}
int func4()
{
 int i,j=10;
 i = j + 10;  
 func5();
}
int func3()
{
   func4();
}
void func2()
{
    int i = 109;
    i++;
   func3();
}
int func1()
{
   func2();
}
int main()
{
func1();
}

Re: IA-64 defect in gdb, any comments what could be the problem

[Jeff Johnston]

Deepak,

   Looking at your output, your Red Hat gdb release is really old.  A number of 
fixes were made for the ia64 after the release of gdb you are using.

   There is an errata for AS2.1 gdb available via rhn that I would suggest you 
look at:

     https://rhn.redhat.com/errata/RHBA-2003-346.html

-- Jeff J.

Kotian, Deepak wrote:
> Hi,
> 
>    We observed a problem on IA-64 Linux(AS 2.1) in backtrace.
>    Please let us know, if there are any inputs .
>    It dumps a core when doing where command.
>    Problem log: problem-ia64.txt attached
>    Target source file which dumps a core is : test.c
> 
>    
>     
> 	
> Thanks and Regards
> Deepak