New version of w3m 0.5.2 Crashes - GDB help needed

[nyc4bos@aol.com]

Bob Heckel <bheckel@gmail.com> writes:

> On Wed, Jan 5, 2011 at 16:22, Christopher Faylor wrote:
>> On Wed, Jan 05, 2011 at 04:16:37PM -0500, nyc4bosaol.com wrote:
>>>nyc4bosaol.com writes:
>>>
>>>Bob created a debug version of w3m for me.
>>>
>>>Here's what I see:
>>>
>>>The crash occurs when doin a `strncmp' in cygwin1.dll:
>>>
>>> Â  Â  Â 4 [main] w3m 3024 exception::handle: Exception: STATUS_ACCESS_VIOLATION
>>> Â  1564 [main] w3m 3024 open_stackdumpfile: Dumping stack trace to w3m.exe.stack
>>>dump
>>>
>>>Program received signal SIGSEGV, Segmentation fault.
>>>0x6110daf5 in strncmp () from /usr/bin/cygwin1.dll
>>>(gdb) bt full
>>>#0 Â 0x6110daf5 in strncmp () from /usr/bin/cygwin1.dll
>>>No symbol table info available.
>>>#1 Â 0x7c85ada0 in OutputDebugStringA ()
>>> Â  from /cygdrive/c/WINDOWS/system32/kernel32.dll
>>>No symbol table info available.
>>>#2 Â 0x40010006 in ?? ()
>>>No symbol table info available.
>>>#3 Â 0x00000000 in ?? ()
>>>No symbol table info available.
>>>(gdb)
>>
>> Looks to me like you need a debugging version of w3m with symbols.
>> You need to find out what's being passed to strncmp, possibly by setting a
>> breakpoint at 0x40110006.

Do you mean 0x40010006 ?

>
> If I did it right, this one includes the symbols:
> http://bheckel.sdf.org/cygwin/w3m/tmp/w3mdebug.tar.bz2

What debugging parameters did you pass it?

Did you pass:

    -g

for ALL of the .c files?

For instance, charset.c doesn't seem to be compiled debuggable.

I didn't see a config.log so all of that extra stuff must be
on your system.

Thanks for your help.

>
> Bob


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple