[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
pico segfaults again because of statusmessage from line 442
From: |
Halim Sahin |
Subject: |
pico segfaults again because of statusmessage from line 442 |
Date: |
Wed, 24 Nov 2010 14:27:11 +0100 |
Hi Andrei,
On Wed, Nov 24, 2010 at 12:35:57PM +0000, Andrei.Kholodnyi at gmail.com wrote:
> > Cannot access memory at address 0x7fff00000000
> ok, this is for sure a not valid address
> hm... it looks like something happens when passing this param to the
> function.
> could you check what address status_info has here
> module_main.c line 132
> ret = module_init(&status_info);
> and then compare it with status_info value inside module_init (char
> **status_info)
Ok lets see:
module_main.c:132
$1 = 0x0
Look good because statusinfo was set to NULL
Inside moduleinit the vallue changes:
$2 = (char **) 0x7fffffffdf38
This is not currect because the i checked the variable before touching
it so it should be NULL as well but it isn't.
BR.
Halim
- pico segfaults again because of statusmessage from line 442, (continued)
- pico segfaults again because of statusmessage from line 442, Christopher Brannon, 2010/11/22
- pico segfaults again because of statusmessage from line 442, Halim Sahin, 2010/11/22
- pico segfaults again because of statusmessage from line 442, Andrei Kholodnyi, 2010/11/22
- pico segfaults again because of statusmessage from line 442, Halim Sahin, 2010/11/22
- pico segfaults again because of statusmessage from line 442, Halim Sahin, 2010/11/22
- pico segfaults again because of statusmessage from line 442, Andrei . Kholodnyi, 2010/11/23
- pico segfaults again because of statusmessage from line 442, William Hubbs, 2010/11/23
- pico segfaults again because of statusmessage from line 442, Halim Sahin, 2010/11/23
- pico segfaults again because of statusmessage from line 442, Halim Sahin, 2010/11/23
- pico segfaults again because of statusmessage from line 442, Andrei . Kholodnyi, 2010/11/24
- pico segfaults again because of statusmessage from line 442,
Halim Sahin <=
- pico segfaults again because of statusmessage from line 442, Andrei Kholodnyi, 2010/11/25
- Message not available
- pico segfaults again because of statusmessage from line 442, Andrei Kholodnyi, 2010/11/26
- pico segfaults again because of statusmessage from line 442, Trevor Saunders, 2010/11/24