get_myaddress problem

ARQUER Stephane stephane.arquer at c-s.fr
Wed Jan 28 09:03:43 UTC 2009


Hello,

I'm trying to debug my problem of get_myadress seg fault, I don't  
understand something strange:

the function  get_myadress use a struct sockaddr_in * as input  
parameter : addr.

but the struct ifreq doesn't have a struct sockaddr_in field ?
The ifr->ifr_addr (ifr->ifr_ifru.ifru_addr) is a struct sockaddr .
Is it normal ?

I work with rtems 4.8.1, get_myaddress v1.4.

Thanks for your help.

sa

> Hello,
>
> I've a problem with the function get_myadress, each time I try to
> connect a client using rpc I obtain a seg fault on the following line
> of get_myadress:
>
> if (((ifreq.ifr_flags & IFF_UP) &&
> 		    ifr->ifr_addr.sa_family == AF_INET &&
> 			!(ifreq.ifr_flags & IFF_LOOPBACK)) ||
> 		    (loopback == 1 && (ifreq.ifr_flags & IFF_LOOPBACK)
> 			&& (ifr->ifr_addr.sa_family == AF_INET)
> 			&& (ifreq.ifr_flags &  IFF_UP))) {
>      *addr = *((struct sockaddr_in *)&ifr->ifr_addr);   <- here the error
>      addr->sin_port = htons(PMAPPORT);
>      gotit = 1;
>      break;
> }
>
> Does anyone have an idea ?
>
> Thanks.
>
> sa
>




----------------------------------------------------------------

Ce message electronique et tous les fichiers joints qu'il contient  
(ci-apres "le message") sont confidentiels et destines exclusivement a  
l'usage des destinataires indiques ou des personnes dument habilitees  
a les recevoir a leur place.

Si vous recevez ce message par erreur, merci de bien vouloir le  
detruire et d'en avertir l'emetteur.

Toute utilisation de ce message non conforme a sa destination, toute  
diffusion ou toute publication totale ou partielle est interdite sauf  
autorisation expresse de l'emetteur.

Les idees et opinions exprimees dans ce message sont celles de son  
auteur et ne representent pas necessairement celles de CS  
Communication & Systemes ou de ses filiales.

Malgre toutes les dispositions prises par CS Communication & Systemes  
et ses filiales pour minimiser les risques de virus, les fichiers  
joints a ce message peuvent contenir des virus qui pourraient  
endommager votre systeme informatique. Il vous appartient d'effectuer  
vos propres controles anti-virus avant d'ouvrir les fichiers joints.  
CS Communication & Systemes et ses filiales declinent toute  
responsabilite pour toute perte ou dommage resultant de l'utilisation  
de ce message et/ou des fichiers joints.

This e-mail and any file attached hereto (hereinafter 'the e-mail')  
are confidential and intended solely for the use of the adressees  
indicated below or the persons duly entitled to receive them in their  
place.

If you receive this e-mail in error, please delete it and notify the sender.

Any use of this e-mail not in accordance with its purpose, any  
dissemination or disclosure, either whole or partial, is prohibited,  
unless formally approved by the sender.

The ideas or opinions expressed in this e-mail are solely those of its  
author and do not necessarily represent those of CS Communication &  
Systeme or its affiliates.

Despite all the measures taken by CS Communication & Systeme and its  
affiliates in order to minimize the risks of virus, the files attached  
to this e-mail may contain virus which could damage your information  
system. You are responsible for processing your own anti-virus  
checking before opening any file attached hereto. Neither CS  
Communication & Systemes, nor its affiliates, shall be held liable for  
any loss or damage due to the use of this e-mail or any file attached  
hereto.






More information about the users mailing list