Frederik Elwert wrote:
> Am Mittwoch, den 30.01.2008, 22:06 +0100 schrieb Ulrich von Zadow:
>> Bug reports are much better if they include code that reproduces the
>> bug. And, since you get a segfault, a stack trace attached to the report
>> would be great.
>
> I included the code. But as "additional information", so it's not in the
> mail, as I just found out. Next time, I'll put it directly into the
> description.
Not necessary, now that I know ;-).
> Could you tell me how to get the stack trace? I'll add it, then.
Very briefly ('#' is your prompt):
# ulimit -c unlimited
# <start whatever causes segfault>
[...]
Segmentation fault (core dumped)
# gdb python core
[...]
(gdb) bt full
[... stack trace is output ...]
(gdb) q
#
The name of the coredump might not be 'core' but core.21257 or something
similar, but you get the idea.
Cheers,
Uli
--
Ulrich von Zadow | +49-172-7872715
Jabber: [EMAIL PROTECTED]
Skype: uzadow
_______________________________________________
libavg-users mailing list
[email protected]
https://mail.datenhain.de/mailman/listinfo/libavg-users
