if your core is from a python program you can check what file/function
was running
use this gdb macro:
define pbt
set $i = 0
set $j = 0
while $i < 1000
select $i
if $eip >= &PyEval_EvalFrame
if $eip < &PyEval_EvalCodeEx
echo c frame #
p $i
echo py frame #
p $j
set $j
Steve Holden wrote:
> su wrote:
>> to find which process dumped core at the promt we give
>>
>> $ file core.28424
>>
>> core.28424: ELF 32-bit LSB core file of 'soffice.bin' (signal 11),
>> Intel 80386, version 1 (SYSV), from 'soffice.bin'
>>
>> from this command we know 'soffice.bin' process du
su wrote:
> to find which process dumped core at the promt we give
>
> $ file core.28424
>
> core.28424: ELF 32-bit LSB core file of 'soffice.bin' (signal 11),
> Intel 80386, version 1 (SYSV), from 'soffice.bin'
>
> from this command we know 'soffice.bin' process dumped core. Now can i
> do the sam
su wrote:
> to find which process dumped core at the promt we give
>
> $ file core.28424
>
> core.28424: ELF 32-bit LSB core file of 'soffice.bin' (signal 11),
> Intel 80386, version 1 (SYSV), from 'soffice.bin'
>
> from this command we know 'soffice.bin' process dumped core. Now can i
> do the
su wrote:
> from this command we know 'soffice.bin' process dumped core. Now can i
> do the same using python i.e. finding which process dumped core? if so
> how can i do it?
You're best bet would be to run the 'file' program using the subprocess
module and parse the output that it generates.
Re
to find which process dumped core at the promt we give
$ file core.28424
core.28424: ELF 32-bit LSB core file of 'soffice.bin' (signal 11),
Intel 80386, version 1 (SYSV), from 'soffice.bin'
from this command we know 'soffice.bin' process dumped core. Now can i
do the same using python i.e. findi
