From: "Kotian, Deepak" <Deepak.Kotian@patni.com>
To: "Kevin Buettner" <kevinb@redhat.com>, <gdb@sources.redhat.com>
Subject: RE: BACKTRACE for coredump in signal handler does come proper for IA-64
Date: Mon, 22 Mar 2004 08:52:00 -0000 [thread overview]
Message-ID: <374639AB1012AA4C840022842AA95BC20182687D@ruby.patni.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]
Kevin,
Please check the differences in the execution log of a small signal handler
program on a normal x86 machine and IA-64 machine.
The sample program is attached.
Please let me know as soon as possible. I just need a justified answer.
Thanks and Regards
Deepak
-----Original Message-----
From: Kevin Buettner [mailto:kevinb@redhat.com]
Sent: Saturday, March 20, 2004 2:06 AM
To: gdb@sources.redhat.com
Subject: Re: BACKTRACE for coredump in signal handler does come proper
for IA-64
On Fri, 19 Mar 2004 23:34:18 +0530
"Kotian, Deepak" <Deepak.Kotian@patni.com> wrote:
> Could one please give a view on this as soon as possible.
>
> Thanks and Regards
> Deepak
>
>
> -----Original Message-----
> From: Kotian, Deepak
> Sent: Thu 3/18/2004 1:21 AM
> To: gdb@sources.redhat.com
> Cc:
> Subject: BACKTRACE for coredump in signal handler does come proper for IA-64
>
>
>
> Hi,
>
> BACKTRACE for coredump in signal handler does come proper for IA-64.
>
> Any inputs what is the reason for it, please let me know.
>
> Thanks and Regards
>
> Deepak
Could you please let us know which version of GDB you're using and
also the operating system (and release info) for you IA-64 system?
You should also supply a testcase demonstrating the problem.
Kevin
[-- Attachment #2: log_sig_x86.txt --]
[-- Type: text/plain, Size: 1896 bytes --]
Script started on Sat Mar 20 12:33:47 2004
root@localhost# uname -a
Linux localhost.localdomain 2.4.9-e.3enterprise #1 SMP Fri May 3 16:35:33 EDT 2002 i686 unknown
root@localhost# gcc -o sig -g ./sig.c
root@localhost# cat sig.c
#include <stdio.h>
#include <signal.h>
void handle(int sig)
{
int *pt = NULL;
printf("handled\n");
*pt = 10;
}
void func1()
{
signal(SIGUSR1, handle);
raise(SIGUSR1);
}
func2()
{
func1();
}
main()
{
func2();
}
root@localhost# ./sig
handled
Segmentation fault (core dumped)
root@localhost# gdb ./sig core
GNU gdb Red Hat Linux (5.1-1)
Copyright 2001 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"...
Core was generated by `./sig'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /lib/i686/libc.so.6...wdone.
Loaded symbols for /lib/i686/libc.so.6
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
#0 0x080484f0 in handle (sig=10) at ./sig.c:7
7 *pt = 10;
(gdb) where
#0 0x080484f0 in handle (sig=10) at ./sig.c:7
#1 <signal handler called>
#2 0x40051b11 in __kill () from /lib/i686/libc.so.6
#3 0x400518ea in raise (sig=10) at ../sysdeps/posix/raise.c:27
#4 0x0804851a in func1 () at ./sig.c:12
#5 0x0804852b in func2 () at ./sig.c:16
#6 0x0804853b in main () at ./sig.c:20
#7 0x4003f657 in __libc_start_main (main=0x8048530 <main>, argc=1,
ubp_av=0xbffed204, init=0x804832c <_init>, fini=0x8048580 <_fini>,
rtld_fini=0x4000dcd4 <_dl_fini>, stack_end=0xbffed1fc)
at ../sysdeps/generic/libc-start.c:129
(gdb) quit
Script done on Sat Mar 20 12:34:29 2004
[-- Attachment #3: log_sig_ia64.txt --]
[-- Type: text/plain, Size: 1449 bytes --]
$ uname -a
Linux Longi1 2.4.21-4.EL #1 SMP Fri Oct 3 17:29:39 EDT 2003 ia64 ia64 ia64 GNU/Linux
$ gcc -o sig -g ./sig.c
$ cat sig.c
#include <stdio.h>
#include <signal.h>
void handle(int sig)
{
int *pt = NULL;
printf("handled\n");
*pt = 10;
}
void func1()
{
signal(SIGUSR1, handle);
raise(SIGUSR1);
}
func2()
{
func1();
}
main()
{
func2();
}
$ ./sig
handled
Segmentation fault (core dumped)
$ gdb sig ./core.21142
GNU gdb Red Hat Linux (5.3.90-0.20030710.40rh)
Copyright 2003 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-gnu"...Using host libthread_db library "/lib/tls/libthread_db.so.1".
Core was generated by `./sig'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /lib/tls/libc.so.6.1...done.
Loaded symbols for /lib/tls/libc.so.6.1
Reading symbols from /lib/ld-linux-ia64.so.2...done.
Loaded symbols for /lib/ld-linux-ia64.so.2
#0 handle (sig=10) at sig.c:7
7 *pt = 10;
(gdb) where
#0 handle (sig=10) at sig.c:7
#1 <signal handler called>
#2 handle (sig=Cannot access memory at address 0xfffffffffffffff0
) at sig.c:6
Cannot access memory at address 0xffffffffffffffe8
(gdb) quit
next reply other threads:[~2004-03-20 7:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-22 8:52 Kotian, Deepak [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-19 20:12 Kotian, Deepak
2004-03-20 8:35 ` Kevin Buettner
2004-03-17 19:46 Kotian, Deepak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=374639AB1012AA4C840022842AA95BC20182687D@ruby.patni.com \
--to=deepak.kotian@patni.com \
--cc=gdb@sources.redhat.com \
--cc=kevinb@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox