Derrick Brashear wrote:
looks like you already lost by the time it crashes.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x4aafd940 (LWP 30735)]
0x003c13078d60 in strlen () from /lib64/libc.so.6
(gdb) bt
#0 0x003c13078d60 in strlen () from
Hi,
I have a problem that I need some advice on how to go on with.
I have a volume dump file, but when trying to read it back volserver
crashes.
The dump was generated under 1.4.8, and the volserver segv appears with
both 1.4.8 and 1.4.11.
VolserLog.old says:
Wed Aug 26 14:56:34 2009
Hartmut Reuter wrote:
Anders Magnusson wrote:
Hi,
I have a problem that I need some advice on how to go on with.
I have a volume dump file, but when trying to read it back volserver
crashes.
The dump was generated under 1.4.8, and the volserver segv appears with
both 1.4.8 and 1.4.11.
Anders Magnusson wrote:
Hi,
I have a problem that I need some advice on how to go on with.
I have a volume dump file, but when trying to read it back volserver
crashes.
The dump was generated under 1.4.8, and the volserver segv appears with
both 1.4.8 and 1.4.11.
VolserLog.old says:
Anders Magnusson wrote:
Hartmut Reuter wrote:
Anders Magnusson wrote:
Hi,
I have a problem that I need some advice on how to go on with.
I have a volume dump file, but when trying to read it back volserver
crashes.
The dump was generated under 1.4.8, and the volserver segv appears
looks like you already lost by the time it crashes.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x4aafd940 (LWP 30735)]
0x003c13078d60 in strlen () from /lib64/libc.so.6
(gdb) bt
#0 0x003c13078d60 in strlen () from /lib64/libc.so.6
#1
Derrick Brashear wrote:
looks like you already lost by the time it crashes.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x4aafd940 (LWP 30735)]
0x003c13078d60 in strlen () from /lib64/libc.so.6
(gdb) bt
#0 0x003c13078d60 in strlen () from
