Dear Dr. Bloom,
Thank you for your suggestions. Yes, I realized after your mail that
different architecture would have different assembly code, which I was
not aware of and assumed every .S file has the same rules.
I will set up an appropriate environment as you both suggested.
Thanks.
On F
On Fri, May 29, 2020 at 1:59 AM Richi Dubey wrote:
>
> This makes sense. Thanks a lot!
>
>
> On Fri, May 29, 2020 at 1:18 PM Sebastian Huber
> wrote:
> >
> > Hello Richi,
> >
> > On 29/05/2020 09:36, Richi Dubey wrote:
> > > Hii,
> > >
> > > I had a small doubt about all the source code/procedure
This makes sense. Thanks a lot!
On Fri, May 29, 2020 at 1:18 PM Sebastian Huber
wrote:
>
> Hello Richi,
>
> On 29/05/2020 09:36, Richi Dubey wrote:
> > Hii,
> >
> > I had a small doubt about all the source code/procedures that a code
> > goes through. Where can I read more about it? For instance
Hello Richi,
On 29/05/2020 09:36, Richi Dubey wrote:
Hii,
I had a small doubt about all the source code/procedures that a code
goes through. Where can I read more about it? For instance, when I am
debugging smpschededf02.exe with gdb, It starts with
bsps/sparc/shared/start/start.S, line 107(Wh
Hii,
I had a small doubt about all the source code/procedures that a code
goes through. Where can I read more about it? For instance, when I am
debugging smpschededf02.exe with gdb, It starts with
bsps/sparc/shared/start/start.S, line 107(Why did it start with
start.s?) and the last line of this
