Re: Initdb problem on debian mips cobalt: Bus error

From: Glyn Astill <glynastill(at)yahoo(dot)co(dot)uk>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, pgsql-general(at)postgresql(dot)org
Subject: Re: Initdb problem on debian mips cobalt: Bus error
Date: 2008-07-22 14:50:01
Message-ID: 103813.82955.qm@web25806.mail.ukl.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>
> Did you actually give a "bt" command, or was that
> just the initial
> output from gdb?
>

Yeah I used the bt command, which gave exactly the same output as the initial output. However you'll have to bear with me here, as I am new to gdb, so there is the possibility I'm just not doing things right at all.

> Another thing to try is looking around the current
> instruction pointer:
>
> x/i $pc
> x/32i $pc-32
>

I've just recompiled again after configuring with --enable-debug, and for completeness here's all the output from gdb:

# gdb /usr/pgsql_src/postgresql-8.3.3/src/test/regress/tmp_check/install/usr/local/pgsql/bin/initdb core
GNU gdb 6.4.90-debian
Copyright (C) 2006 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 "mipsel-linux-gnu"...Using host libthread_db library "/lib/libthread_db.so.1".

warning: core file may not match specified executable file.
Core was generated by `/usr/pgsql_src/postgresql-8.3.3/src/test/regress/tmp_check/install/usr/local/pg'.
Program terminated with signal 10, Bus error.
#0 0x007572d0 in ?? ()
(gdb) bt
#0 0x007572d0 in ?? ()
warning: GDB can't find the start of the function at 0x7572d0.

GDB is unable to find the start of the function at 0x7572d0
and thus can't determine the size of that function's stack frame.
This means that GDB may be unable to access that stack frame, or
the frames below it.
This problem is most likely caused by an invalid program counter or
stack pointer.
However, if you think GDB should simply search farther back
from 0x7572d0 for code which looks like the beginning of a
function, you can increase the range of the search using the `set
heuristic-fence-post' command.
#1 0x007572d0 in ?? ()
warning: GDB can't find the start of the function at 0x7572d0.
Previous frame identical to this frame (corrupt stack?)
(gdb) set heuristic-fence-post 10000000
(gdb) bt
#0 0x007572d0 in ?? ()
warning: GDB can't find the start of the function at 0x7572d0.
#1 0x007572d0 in ?? ()
warning: GDB can't find the start of the function at 0x7572d0.
Previous frame identical to this frame (corrupt stack?)
(gdb) x/i $pc
0x7572d0: Cannot access memory at address 0x7572d0
(gdb) x/32i $pc
0x7572d0: Cannot access memory at address 0x7572d0
(gdb)

__________________________________________________________
Not happy with your email address?.
Get the one you really want - millions of new email addresses available now at Yahoo! http://uk.docs.yahoo.com/ymail/new.html

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2008-07-22 15:03:07 Re: Initdb problem on debian mips cobalt: Bus error
Previous Message Tom Lane 2008-07-22 14:25:51 Re: Problems Restarting PostgreSQL Daemon