threads/2130: Cannot access thread memory x86_64

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

threads/2130: Cannot access thread memory x86_64

Sami Kerola

>Number:         2130
>Category:       threads
>Synopsis:       Cannot access thread memory x86_64
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri May 26 12:08:01 GMT 2006
>Originator:     [hidden email]
>Release:        gdb-
Linux lohi5 2.4.21-37.0.1.ELsmp #1 SMP Wed Jan 11 18:35:39 EST 2006 x86_64 x86_64 x86_64 GNU/Linux
Dual AMD Opteron(tm) Processor 244
I compiled new bind and it dropped core. Debugging core gives backtrace from active thread but not from other three thread. Like this:

> ../gdb- sbin/named run/core.1486
(gdb) bt
#0  0x0000002a95b06745 in raise () from /lib64/tls/
#1  0x0000002a95b07eb3 in abort () from /lib64/tls/
#2  0x0000000000413f0a in assertion_failed (file=0x589b50 "query.c",
    line=1765, type=isc_assertiontype_insist,
    cond=0x589d19 "result != (((1) << 16) + 51)") at main.c:159
#16 0x0000000000000000 in ?? ()
(gdb) info threads
  5 process 1486  0x0033c00fc031736e in ?? ()
  4 process 1488  0x0100020011c0b9c0 in ?? ()
  3 process 1489  0x00010002000cc000 in ?? ()
  2 process 1490  0x6f01000100020059 in ?? ()
* 1 process 1487  0x0000002a95b06745 in raise () from /lib64/tls/
(gdb) thread 2
[Switching to thread 2 (process 1490)]#0  0x6f01000100020059 in ?? ()
(gdb) bt
#0  0x6f01000100020059 in ?? ()
Cannot access memory at address 0x3b6f010001000200

I tried also debug running process but process stops immediately when it's debugged. By trying to command continue from gdb does not help, process stops immediately after continue. Kill -SIGCONT will continue stopped process, but tracing is lost. There seems to be no way to find out why bind crashes.
Install Red Hat Enterprise Linux WS release 3 (Taroon Update 7) on Sun Fire v40z, compile latest bind and you'll see exactly what I. I guess there's easier ways to repeat this problem, I am open to suggestions.
I hope you don't expect me to know how to fix this one.