Re: problem in pseudo header

When I stepped through to the seek_read() function, I realized that
wth->pseudo_header and pseudo_header point to different memory addresses. I
was actually expecting that they are going to be the same. Thats when I
tried setting values in the pseudo_header and it worked.

Some of early/ core members of ethereal-dev might be able to shed light on
what wth->pseudo_header is pointing to. Possible stale info from that last
packet read in the read() function during summary display.

Ravi.

On 5/29/06, Raman Singla <[email protected]> wrote:
>
>  Thanks Mr. Ravi the problem is sorted out by this but i still can't
> figure out why is it so.
> whereas pseudo_header-> or wtap->pseudo_header. is one & same thing
>
> when i did with pseudo_header-> it worked out.
>
> thank you Mr. Ravi.
>
> ----- Original Message -----
> *From:* Ravi Kondamuru <[email protected]>
> *To:* Ethereal development <[email protected]>
> *Sent:* 2006 May 30 8:14 AM
> *Subject:* Re: [Ethereal-dev] problem in pseudo header
>
> seek_read() function has
>    wtap* wth and union wtap_pseudo_header* pseudo_header
> as arguments.
>
> Make sure that in seek_read you are setting
>
> pseudo_header.dec_hdr->step
> and not
> wtap->pseudo_header.dec_hdr->step
>
> From your mail, it looks like you are setting in the wtap->pseudo_header.
>
> thanks,
> Ravi.
>
> On 5/29/06, Raman Singla <[email protected]> wrote:
> >
> >  i read ur answer, see i m just using these values directly, like
> > big/little endian or message_type.(depending on message type it will decode
> > for that message.
> >
> > in simple language - i have to get that pseudo header value in one
> > variable in dissector while pseudo header is read through seek_read.
> >
> >
> >  ----- Original Message -----
> > *From:* Ravi Kondamuru <[email protected]>
> > *To:* Ethereal development <[email protected]>
> > *Sent:* 2006 May 30 3:10 AM
> > *Subject:* Re: [Ethereal-dev] problem in pseudo header
> >
> > Raman,
> >
> > Good question!! I had posted a similar problem sometime back.
> > http://www.ethereal.com/lists/ethereal-dev/200605/msg00149.html
> >
> > After reading your question I just realized that the pseudo_header has
> > to be re-populated all over again in the seek_read function. I was not doing
> > it. Thanks for your question, I might have found just the problem I have
> > been struggling with for last 2 weeks.
> >
> > thanks,
> > Ravi.
> >
> > On 5/29/06, Raman Singla <[email protected]> wrote:
> > >
> > >  hi all,
> > >
> > > I m writing decoder for new capture format. (dectrace).
> > >
> > > I have made a pseudo_header which will carry info of frame_no,
> > > sender,receiver etc.
> > >
> > > in wiretap : in read function the i m loading pseudo_header with
> > > appropiate data & i m able to use this in dissector. (for column information
> > > etc)
> > >
> > > the problem :
> > > when i m loading pseudo_header in seek_read (it is showing correct
> > > info) e.g.
> > > in wtap->pseudo_header.dec_hdr->step
> > > but the same information in dissector is replaced by 0
> > > e.g. value of pinfo->pseudo_header.dec_hdr->step is 0.
> > >
> > > i m unable to understand why the same info if loaded through read is
> > > raching correct at dissector when the same is loaded from seek_read is
> > > replaced by 0 somewhere between exit of seek & entry to dissector.
> > >
> > > regards
> > >
> > > Raman
> > > Ext - 1667
> > >
> > > _______________________________________________
> > > Ethereal-dev mailing list
> > > [email protected]
> > > http://www.ethereal.com/mailman/listinfo/ethereal-dev
> > >
> > >
> > >
> >  ------------------------------
> >
> > _______________________________________________
> > Ethereal-dev mailing list
> > [email protected]
> > http://www.ethereal.com/mailman/listinfo/ethereal-dev
> >
> >
> > _______________________________________________
> > Ethereal-dev mailing list
> > [email protected]
> > http://www.ethereal.com/mailman/listinfo/ethereal-dev
> >
> >
> >
>  ------------------------------
>
> _______________________________________________
> Ethereal-dev mailing list
> [email protected]
> http://www.ethereal.com/mailman/listinfo/ethereal-dev
>
>
> _______________________________________________
> Ethereal-dev mailing list
> [email protected]
> http://www.ethereal.com/mailman/listinfo/ethereal-dev
>
>
>

_______________________________________________
Ethereal-dev mailing list
[email protected]
http://www.ethereal.com/mailman/listinfo/ethereal-dev