Will keep this in mind. Thanks.
On Thu, Jul 2, 2020 at 4:05 PM Jiri Gaisler wrote:
> Note that single-stepping of smp code at instruction-level might affect
> the timing of the execution. During single-stepping, only one core is
> advanced while the others stay halted. If you are trying to catch
Note that single-stepping of smp code at instruction-level might affect the
timing of the execution. During single-stepping, only one core is advanced
while the others stay halted. If you are trying to catch a race condition then
the timing impact might change the program behavior. Shorter burst
Yeah, this makes a lot of sense.
Mr. Huber also told me a similar story about qemu using -O0 optimizations
which are easier to debug.
Thank you.
On Wed, Jul 1, 2020 at 8:03 PM Gedare Bloom wrote:
> On Wed, Jul 1, 2020 at 5:32 AM Richi Dubey wrote:
> >
> > Dear Dr. Gaisler,
> >
> > There's some
On Wed, Jul 1, 2020 at 5:32 AM Richi Dubey wrote:
>
> Dear Dr. Gaisler,
>
> There's something that I am getting stuck at while trying to debug an smp03
> (https://git.rtems.org/rtems/tree/testsuites/smptests/smp03/init.c) test
> suite with gdb running on sis.
>
> I started sis with the command:
Dear Dr. Gaisler,
There's something that I am getting stuck at while trying to debug an smp03
(https://git.rtems.org/rtems/tree/testsuites/smptests/smp03/init.c) test
suite with gdb running on sis.
I started sis with the command:
---
Thanks a lot! It is working now after I set appropriate breakpoints.
On Tue, May 26, 2020 at 11:58 PM Jiri Gaisler wrote:
>
>
> On 5/26/20 2:55 PM, Richi Dubey wrote:
> > Hii,
> >
> > Thank you for your replies. I did not load the program before
> > executing run on gdb. Now it works fine.
> >
>
On 5/26/20 2:55 PM, Richi Dubey wrote:
> Hii,
>
> Thank you for your replies. I did not load the program before
> executing run on gdb. Now it works fine.
>
> However, I need your help with one more thing. When I run gdb with
> stepi or nexti to see how the code runs from the beginning to the end
Hii,
Thank you for your replies. I did not load the program before
executing run on gdb. Now it works fine.
However, I need your help with one more thing. When I run gdb with
stepi or nexti to see how the code runs from the beginning to the end,
gdb always ends up going in an infinite loop in har
On 5/25/20 4:30 PM, Richi Dubey wrote:
> Hii everyone,
>
> When I am executing smpschededf02.exe on my leon3 bsp running on
> sparc5 with sparc-rtems5-sis with -m 4 -leon3 option, it fails to
> execute properly.
>
> I have built leon3 with --enable-smp option and I am guessing the
> execution fa
On 25/05/2020 16:30, Richi Dubey wrote:
When I am executing smpschededf02.exe on my leon3 bsp running on
sparc5 with sparc-rtems5-sis with -m 4 -leon3 option, it fails to
execute properly.
I have built leon3 with --enable-smp option and I am guessing the
execution fails because I don not see a
On executing run again on gdb, I am getting the following error:
0x in ?? ()
(gdb) run
The program being debugged has been started already.
Start it from the beginning? (y or n) y
../../gdb-9.1/gdb/thread.c:95: internal-error: thread_info*
inferior_thread(): Assertion `tp' failed.
A proble
11 matches
Mail list logo
