[Fwbuilder-discussion] Re: fwbuilder-2.0.8-b:619 segfault

[Vadim K. <va...@vk...>]

On Jul 15, 2005, at 4:10 AM, Tom Diehl wrote:

>>>>
>>>> On Jul 14, 2005, at 2:45 PM, Tom Diehl wrote:
>>>>
>>>>
>>>>
>>>>> Hi all,
>>>>>
>>>>> I have fwbuilder fwbuilder-2.0.8-b:619 running on an em64t machine
>>>>> on RHEL 4.
>>>>> When I run it from the console everything works fine. The problem
>>>>> is when I
>>>>> try to run it remotely via an ssh tunnel and x forwarding it dumps
>>>>> core.
>>>>>
>>>>> Any ideas what might be causing this??
>>>>>
>>>>> FWIW the remote machine is an i386 machine. xclock runs just fine
>>>>> over the
>>>>> same tunnel.
>>>>>
>>>>>
>>>>
>>
>> did you compile it on that RHEL 4 machine yourself ? If so, try to
>> run the binary from src/gui directory instead of one installed in /
>> usr/local/bin, make it dump core and then run this command
>>
>
> I used your src.rpm to build it. I do not have it in any of the paths
> you suggest. The exact command I used to build it was
> "rpmbuild -ba --clean *.spec".
>

the source should be in /usr/src/redhat/BUILD/fwbuilder-2.0.8/   
directory. Please check if it is there, and if yes, rebuild the  
unstripped executable as follows:

cd /usr/src/redhat/BUILD/fwbuilder-2.0.8/src/gui
make

Then run it from that directory over ssh tunnel

cd /usr/src/redhat/BUILD/fwbuilder-2.0.8/src/gui
./fwbuilder

it should dump core, check the core file name:

ls core*

and produce stack trace (run this command in the same directory)

gdb fwbuilder core.*

--vk


>
>>
>> gdb fwbuilder core.NNNN
>>
>> where core.NNNN is the core file. Once gdb presents its command
>> prompt, type "bt" and hit enter and send the output.
>>
>
> I installed the debug rpm and here is what I got:
>
> (gdb) bt
> #0  0x000000000065bd74 in __res_hostalias ()
> Cannot access memory at address 0xbfffb864
> (gdb)
>
> Regards,
>
> Tom Diehl        td...@ro...        Spamtrap address  
> mt...@ro...
>