["Raman Singla" <ramans@xxxxxxxxxxxxxxxxxxx>]

hi,

report_open_failure is for pluggins not for dissectors.

However i see that there is linking issues which i m unable to resolove. Is
this possible..

in ethereal root have a file in which there will be a function which will
call intern simple_dialog with paramaters. & this is working fine. (file.c
in ethereal root uses simple_dialog but file.c is called by another program
but in our case we will be calling our function either from wieretap or
epan/dissector)

problem is if i want to call this function through wiretap or epan/dissector
it gives undefined reference (linking issues). i m not sure but if somehow
if we change the way linking is happening we may come to a solution.

This is a feature which is badly required. (Every thing is ready just need
to linked).

regards,
raman


----- Original Message ----- 
From: "Jaap Keuter" <jaap.keuter@xxxxxxxxx>
To: "Ethereal development" <ethereal-dev@xxxxxxxxxxxx>
Sent: 2006 Jun 02 11:02 AM
Subject: Re: [Ethereal-dev] error in printing error message using
simple_dialog


> Hi,
>
> The ASN1 plugin has this same issue. It uses report_open_failure for that.
> Have a look at plugins/asn1/packet-asn1.c how this is done.
>
> Thanx,
> Jaap
>
> On Fri, 2 Jun 2006, Raman Singla wrote:
>
> > hi,
> > there is a file (trace.def) which is having all the structure format
telling
> > how the hexdumps should be decode for gprs messages
> >
> > suppose system is unable to open this file, there should be a error
message
> > indicating that error file is missing.
> >
> > Here when i say error messages they are not with respect to packets,
they
> > are with respect to other issues. before becoding begins it will ensure
> > these parameters & if it unable to set an working environment it will
pop up
> > an error message. ofcause packet-related error will be using
proto_add_text.
> >
> > Similarly in wiretap (i have written for a new capture file format, if
> > endian type is missing (file can be in either big/little format then it
> > won't proceed further & prompt a error messsage)
> >
> >   simple_dialog(ESD_TYPE_ERROR, ESD_BTN_OK, dec_err_msg);
> > does this with appropriate paramaters. but here in my case it is giving
> > error on both platform linux/win.
> >
> > error on LINUX
> > it is giving an linking error.
> > epan/./libs/libethereal.so: undefined reference to 'simple_dialog'
> >
> > err on WINDOWS
> > dissectors.lib(packet-dec.obj) : error LNK2001: unresolved external
symbol
> > _simp
> > le_dialog
> > libethereal.dll : fatal error LNK1120: 1 unresolved externals
> > NMAKE : fatal error U1077: 'link' : return code '0x460'
> > Stop.
> > NMAKE : fatal error U1077: '"C:\Apps_32\MICROSOFT VISUAL
> > STUDIO\VC98\BIN\NMAKE.E
> > XE"' : return code '0x2'
> > Stop.
> >
> > regards,
> > raman
> >
> > ----- Original Message -----
> > From: "John R." <jhoger@xxxxxxxxx>
> > To: "Ethereal development" <ethereal-dev@xxxxxxxxxxxx>
> > Sent: 2006 Jun 02 4:23 AM
> > Subject: Re: [Ethereal-dev] error in printing error message using
> > simple_dialog
> >
> >
> > > On 6/1/06, Raman Singla <ramans@xxxxxxxxxxxxxxxxxxx> wrote:
> > > > Hi,
> > > >
> > > > I want to use simple_dialog function defined in
"gtk/simple_dialog.c"
> > for
> > > > printing error messages.
> > >
> > > Upon what event would trigger such a dialog? Every time the packet is
> > > selected? It seems like a very bad idea since you would end up stuck
> > > in a dialog box every time the packet is dissected. If you had a bunch
> > > of these packets, you would end up stuck in dialog boxes as you try to
> > > navigate between packets in the display.... yikes!
> > >
> > > -- John.
> > > _______________________________________________
> > > Ethereal-dev mailing list
> > > Ethereal-dev@xxxxxxxxxxxx
> > > http://www.ethereal.com/mailman/listinfo/ethereal-dev
> >
> > _______________________________________________
> > Ethereal-dev mailing list
> > Ethereal-dev@xxxxxxxxxxxx
> > http://www.ethereal.com/mailman/listinfo/ethereal-dev
> >
>
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-dev

_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev