[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#22120: Another backtrace
From: |
Eli Zaretskii |
Subject: |
bug#22120: Another backtrace |
Date: |
Thu, 10 Dec 2015 21:02:30 +0200 |
> From: Eric Hanchrow <eric.hanchrow@gmail.com>
> Date: Thu, 10 Dec 2015 18:42:19 +0000
>
> What little I could get of the variables' values is at the bottom.
It doesn't tell much.
Can you try reproducing this in an unoptimized build? It's very hard
to debug optimized code when we suspect some more or less random
corruption of values. If the problem happens in an unoptimized build,
we won't need to look so hard for bad values.
Also, it looks like you configured with --enable-check-lisp-object-type,
is that right? If so, please configure without it, that would allow
to see many values directly in the backtrace, instead of asking you to
print them in GDB.
Thanks.
bug#22120: 25.1.50; segfault while running circe, John Wiegley, 2015/12/08
bug#22120: Another backtrace, Eric Hanchrow, 2015/12/10
- bug#22120: Another backtrace,
Eli Zaretskii <=
bug#22120: Another backtrace, Eric Hanchrow, 2015/12/12
- bug#22120: Another backtrace, Eli Zaretskii, 2015/12/13
- bug#22120: Another backtrace, Eric Hanchrow, 2015/12/13
- bug#22120: Another backtrace, Eli Zaretskii, 2015/12/13
- bug#22120: Another backtrace, Eric Hanchrow, 2015/12/13
- bug#22120: Another backtrace, Eli Zaretskii, 2015/12/13
- bug#22120: Another backtrace, Eric Hanchrow, 2015/12/13
- bug#22120: Another backtrace, Eli Zaretskii, 2015/12/13