Hi Kawai:
I find that if set coredump_filter to 0x32, the core file can't gdb
work correctly.
because the value of anon_vma for stack or brk vma is also not NULL.
in function vma_dump_size, stack and brk vma will not dump if
FILTER(ANON_PRIVATE) is 0.
if ( vma->anon_vma && FILTER(ANON_PRIVATE) )
I think there are no way to tell the kernel didn't dump guest os memory.
for current kernel, /proc//coredump_filter only support the
following 7 memory types.
- (bit 0) anonymous private memory
- (bit 1) anonymous shared memory
- (bit 2) file-backed private memory
- (bit 3) file-backed sha
2011/6/24 Jan Kiszka :
> On 2011-06-24 10:55, Jan Kiszka wrote:
>> On 2011-06-24 10:24, lidong chen wrote:
>>> 2011/6/23 Jan Kiszka :
On 2011-06-23 15:56, lidong chen wrote:
>>> is it safe to register another signal handler?
>>> if somebody know the reason, please tell me.
>>>
On 2011-06-24 10:55, Jan Kiszka wrote:
> On 2011-06-24 10:24, lidong chen wrote:
>> 2011/6/23 Jan Kiszka :
>>> On 2011-06-23 15:56, lidong chen wrote:
>> is it safe to register another signal handler?
>> if somebody know the reason, please tell me.
>>
>> and is it worth to do this?
On 2011-06-24 10:24, lidong chen wrote:
> 2011/6/23 Jan Kiszka :
>> On 2011-06-23 15:56, lidong chen wrote:
> is it safe to register another signal handler?
> if somebody know the reason, please tell me.
>
> and is it worth to do this?
>>> because the core dump file is too big,
2011/6/23 Jan Kiszka :
> On 2011-06-23 15:56, lidong chen wrote:
is it safe to register another signal handler?
if somebody know the reason, please tell me.
and is it worth to do this?
>>>
>> because the core dump file is too big, and the time of core dump is too long.
>> I do a
On 2011-06-23 15:56, lidong chen wrote:
>>> is it safe to register another signal handler?
>>> if somebody know the reason, please tell me.
>>>
>>> and is it worth to do this?
>>
> because the core dump file is too big, and the time of core dump is too long.
> I do a test, for a guest which have 9.
2011/6/23 Jan Kiszka :
> On 2011-06-23 11:05, lidong chen wrote:
>> Hi all,
>>
>> I didn't understand why need block all signal except SIGBUS SIGIPI for
>> vcpu thread?
>
> For simplicity reasons: All other expected signals are handled by the
> io-thread or other helper threads. Those must never be
On 2011-06-23 11:05, lidong chen wrote:
> Hi all,
>
> I didn't understand why need block all signal except SIGBUS SIGIPI for
> vcpu thread?
For simplicity reasons: All other expected signals are handled by the
io-thread or other helper threads. Those must never be processed by the
vcpus. So we bl
ion when abnormally exit.
> For example, if qemu-kvm exit by segmentation fault, there are no
> information in /var/log/libvirt/qemu/xx.log.
>
> so i want to solve this by collect some information when qemu-kvm exit.
>
> my idea is register some signal handler, and print some debug
&
I find qemu-kvm only output a little information when abnormally exit.
For example, if qemu-kvm exit by segmentation fault, there are no
information in /var/log/libvirt/qemu/xx.log.
so i want to solve this by collect some information when qemu-kvm exit.
my idea is register some signal handler
11 matches
Mail list logo
