This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Still on ethernet configuration


> > (gdb) bt
> > #0  i82559_configure (p_i82559=0xc006994c, promisc=393216, oversized=1,
> >     multicast_all=0)
> >     at 
> > /opt/ecoscvs.10-13-2002/ecos/packages/devs/eth/intel/i82559/current/src/if_i82559.c:3183
> > #1  0xc0021594 in i82559_start (sc=0xc0069fd4, enaddr=0xc50600 "",
> >     flags=-1073298004)
> >     at 
> > /opt/ecoscvs.10-13-2002/ecos/packages/devs/eth/intel/i82559/current/src/if_i82559.c:1619
> > #2  0xc011baf8 in stack ()
> > (gdb) s
> > 
> > I'm also issuing the "bt" command but honestly I don't see how it tells me 
> > whether the stack is good or not. After the last "s" command
> > the program never returns.

bt stands for backtrace. It shows you all the function calls to get to
where you are. To me, this stack trace looks wrong. Its saying that
i82559_start called i82559_configure. This is correct, check the
sources. But its not showing what called i82559_start. If i remember
correctly, you said it stops in init_net. So init_net will be making
an ioctl call. The generic ioctl call will call the network ioctl. The
network ioctl into the ethernet ioctl,.. ,.., You should see all these
in the backtrace.

If you have not done much debugging before with gdb, i suggest you
read the first section of the gdb info pages. It a tutorial going
through some of the basic concepts of how to use gdb.

        Andrew

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]