Prev: Multiple heap overflows in xine-lib
Next: 2.2 kernel based os?
From: MatthewK on 29 Mar 2008 08:39
* Chris Sorenson <csoren(a)isd.net> wrote:
> MatthewK wrote:
>> After a recent trist with freebsd and openbsd I discovered w3m. On
>> my slackware 12 box whenever I try to use the program in the console I
>> get a segmentation fault. I have the GC library and have used both
>> source and package versions of w3m. It works fine under X as long as
>> I'm not using screen.
>>
>
> When you say you used the source version, do you mean you compiled it
> yourself? If you compiled it with the debugging symbols (and did not
> strip the resulting binary), you can run it in the debugger, and it
> will tell you what's going on...
>
>
> gdb w3m
>
> (gdb) run
>

Yeah, I compiled it myself. Thanks for the tip, I'm no programmer so a
big part of my computer knowledge is missing but I'm sure this tip will
prove useful.

matthew
From: Chris Sorenson on 29 Mar 2008 17:15
>>
>>When you say you used the source version, do you mean you compiled it
>>yourself? If you compiled it with the debugging symbols (and did not
>>strip the resulting binary), you can run it in the debugger, and it
>>will tell you what's going on...
>>
>>
>>gdb w3m
>>
>>(gdb) run
>>
>
>
> Yeah, I compiled it myself. Thanks for the tip, I'm no programmer so a
> big part of my computer knowledge is missing but I'm sure this tip will
> prove useful.
>

Passing -g as a parameter to the compiler includes all the debugging
symbols in the resulting binary. If the app usees autoconf to generate
the makefiles then the default is to pass -g.

You can check the binary using the `file' command, if the debugging
symbols are in there, it will tell you. If not, it will say `stripped'.

From: slakmagik on 29 Mar 2008 22:36
On 2008-03-26 Wed 18:15:20, MatthewK wrote:
> After a recent trist with freebsd and openbsd I discovered w3m. On
> my slackware 12 box whenever I try to use the program in the console I
> get a segmentation fault. I have the GC library and have used both
> source and package versions of w3m. It works fine under X as long as
> I'm not using screen.
>
> In my favorite livecd, grml, w3m works fine in the console. Does anybody
> have and idea of what is going on here? Did I miss an option in
> ./configure? The documentation for w3m seems poor and the only thing I
> really like about w3m over links2 is the keybindings.
>

I can confirm the segfault. Try

../configure --with-termlib="terminfo ncurses"

- apparently something goes squirelly when it links against termcap but
it seems to be behaving itself with me when linking to ncurses.

I'm not sure if this is the best solution but if this seems to work,
I'll try to get a bugfix into SBo. (I know that's not what you were
using, but if you wanted to test it I wouldn't object.) ;)

(An even quicker fix is just to lie and tell it your TERM is xterm even
in 'linux' or 'screen'.)
From: MatthewK on 5 Apr 2008 15:40
* Chris Sorenson <csoren(a)isd.net> wrote:
>>>
> Passing -g as a parameter to the compiler includes all the debugging
> symbols in the resulting binary. If the app usees autoconf to generate
> the makefiles then the default is to pass -g.
>
> You can check the binary using the `file' command, if the debugging
> symbols are in there, it will tell you. If not, it will say `stripped'.
>

Thanks, I'll probably check this out in a week or two.

matthew
ohio
From: MatthewK on 5 Apr 2008 15:41
* slakmagik <j(a)hostname.invalid> wrote:
> On 2008-03-26 Wed 18:15:20, MatthewK wrote:
>
> I can confirm the segfault. Try
>
> ./configure --with-termlib="terminfo ncurses"
>
> - apparently something goes squirelly when it links against termcap but
> it seems to be behaving itself with me when linking to ncurses.
>
> I'm not sure if this is the best solution but if this seems to work,
> I'll try to get a bugfix into SBo. (I know that's not what you were
> using, but if you wanted to test it I wouldn't object.) ;)
>
> (An even quicker fix is just to lie and tell it your TERM is xterm even
> in 'linux' or 'screen'.)

cool...more things to play with.

Thank you.

matthew
ohio
 | 
Pages: 1
Prev: Multiple heap overflows in xine-lib
Next: 2.2 kernel based os?