Re: [Monotone-devel] Upgrade from .31 to .32 mtn list keys causes segmentation fault

[Nathaniel Smith]

On Wed, Feb 14, 2007 at 04:53:53PM -0700, Matthew Sielski wrote:
>    mtn: fatal signal: Segmentation fault
>    this is almost certainly a bug in monotone.
>    please send this error message, the output of 'mtn --full-version',
>    and a description of what you were doing to address@hidden
>    do not send a core dump, but if you have one,
>    please preserve it in case we ask you for information from it.
>    Segmentation fault
>    $ mtn --full-version
>    monotone 0.32 (base revision: 3f0fa5c1d232d37d47f6436fe74919dd3cd003b1)
>    Running on          : Linux 2.6.16-1.2115_FC4_HPTRAID #1 SMP Mon Jun 12
>    16:13:33 MST 2006 i686
>    C++ compiler        : GNU C++ version 4.0.2 20051125 (Red Hat 4.0.2-8)
>    C++ standard library: GNU libstdc++ version 20051125
>    Boost version       : 1_33_1
>    Changes since base revision:
>    unknown

How did you install 0.32?  (From a package, built it yourself, ...?)
What does 'ldd mtn' say on the 0.32 binary?

Usually this kind of segmentation fault is a toolchain problem, though
the fact that you were able to migrate the old database in that case
is a bit weird...

If you run 'gdb --args mtn ls keys', and then type "run" to run the
program, and then "backtrace" when it gives the segfault, then what
output do you get?

-- Nathaniel

-- 
"Of course, the entire effort is to put oneself
 Outside the ordinary range
 Of what are called statistics."
  -- Stephan Spender