Re: fc3 ethereal debuginfo - incomplete ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Pawel wrote:
David Timms writes:
 > Pawel wrote:
 > > Hallo group members!
> > > > I am trying to debug ethereal, namely files:
 > > ./ethereal-0.10.14/epan/dissectors/packet-h225.c
 > > ./ethereal-0.10.14/epan/dissectors/packet-h450.c
 > > but none of them appear to exist in ethereal-debuginfo-0.10.14-1.FC3.1.i386.rpm which I downloaded from rpm search site. It of course matches ethereal version installed on my machine.
> > > > I know that they exist, because they were created when I compiled ethereal-0.10.14-1.FC3.1.src.rpm on my local machine: > > > > /usr/src/redhat/BUILD/ethereal-0.10.14/epan/dissectors/packet-h225.c
 > > /usr/src/redhat/BUILD/ethereal-0.10.14/epan/dissectors/packet-h450.c
> > > > As You know, building ethereal with the following command... :
 > > prompt$ rpmbuild -bb /usr/src/redhat/SPECS/ethereal.spec
> > > > ... also creates /usr/src/redhat/RPMS/i386/ethereal-debuginfo-0.10.14-1.FC3.1.i386.rpm. > > > > prompt$ rpm -qpl /usr/src/redhat/RPMS/i386/ethereal-debuginfo\
 > -0.10.14-1.FC3.1.i386.rpm | egrep "(packet-h450.c|packet-h450.c)"
 > -----------------------------------/\       --            --   /\
> > not sure if the () are needed, and you repeated the match term.
You are right. I misstyped it. I meant "(packet-h450.c|packet-h225.c)",
but it does not change the case:

prompt# rpm -ql ethereal-debuginfo | grep packet-h450.c
prompt# prompt# rpm -ql ethereal-debuginfo | grep packet-h225.c prompt# # None of them exist

 > did you install the xxx-debuginfo and try to use it ?
Yes, this was my preliminary step. When I did not find it I decided to build ethereal on my local machine.
prompt# rpm -qa | grep ethereal
ethereal-0.10.14-1.FC3.1
ethereal-gnome-0.10.14-1.FC3.1
ethereal-debuginfo-0.10.14-1.FC3.1

 > will the files be .c ?
Answering myself: yes.

I installed fc6 wireshark debuginfo. There is some files that include 225 but none that mention 450. Whether this is a change in application structure, I dont know. If you are sure it should be there, perhaps it is a packaging bug - you might be able to work out what needs to change to get the correct debuginfo built.

You might also be able to extract and config the source archive itself for debug. {I am not much experienced in this area}

DaveT.


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux