Mailinglist Archive: opensuse-programming (52 mails)

< Previous Next >
Re: [suse-programming-e] diagnosing a stack corruption
  • From: Per Jessen <per@xxxxxxxxxxxx>
  • Date: Mon, 24 Apr 2006 22:37:54 +0200
  • Message-id: <e2jcv2$mfq$2@xxxxxxxxxxxxxxxx>
Anders Johansson wrote:

> On Monday 24 April 2006 22:22, Jerry Feldman wrote:
>> For one, make sure that a core file is produced. Then run GDB on the
>> core file. That will point you at the segfault, then try to do a
>> backtrace (the bt command) from there. Stack corruptions do tend to
>> be messy because you lose context.
>
> You might get some idea just by displaying the contents of the stack.
> Seeing what it is that has been written there could be a big clue
> towards tracking down what is writing it

Yes, I understand that - my problem is that I suspect the corruption is
being done by an external library (libclamav), and I'm not sufficiently
familiar with that to immediately spot something odd in the stack.


/Per Jessen, Z├╝rich


< Previous Next >
Follow Ups