All of lore.kernel.org
 help / color / mirror / Atom feed
From: Parag Warudkar <kernel-stuff@comcast.net>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: 2.6.13-mm1 X86_64: All 32bit programs segfault
Date: Thu, 08 Sep 2005 09:08:06 -0400	[thread overview]
Message-ID: <432037B6.10307@comcast.net> (raw)
In-Reply-To: <200509080744.06326.ak@suse.de>

Andi Kleen wrote:

>If you catch a crash in gdb and type x/i $pc what do you see?
>
>-Andi
>  
>
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1431820864 (LWP 2839)]
0x00c40471 in __pthread_initialize_minimal_internal ()
   from /lib/libpthread.so.0
(gdb) x/i $pc
0xc40471 <__pthread_initialize_minimal_internal+78>:    mov    
0x2e8(%eax),%edx
(gdb) info registers
eax            0x0      0
^^^^^^^^^^^^^^^^^^
ecx            0x5557da88       1431820936
edx            0x1      1
ebx            0xffffd4a8       -11096
esp            0xffffd1e4       0xffffd1e4
ebp            0xffffd4a8       0xffffd4a8
esi            0x5557da40       1431820864
edi            0x0      0
eip            0xc40471 0xc40471
eflags         0x10202  66050
cs             0x23     35
ss             0x2b     43
ds             0x2b     43
es             0x2b     43
fs             0x0      0
gs             0x63     99


  reply	other threads:[~2005-09-08 13:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-08  3:54 2.6.13-mm1 X86_64: All 32bit programs segfault Parag Warudkar
2005-09-08  4:00 ` Andi Kleen
2005-09-08  5:10   ` Parag Warudkar
2005-09-08  5:44     ` Andi Kleen
2005-09-08 13:08       ` Parag Warudkar [this message]
2005-09-08  8:44     ` Andrew Morton
2005-09-08  8:57       ` Andi Kleen
2005-09-08 12:57       ` Parag Warudkar

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=432037B6.10307@comcast.net \
    --to=kernel-stuff@comcast.net \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.