Re: Exception return

On Thu, 16 Dec 2021 at 20:07, abhijeet inamdar wrote: > > If I won't make that change it gives me immediate error as follows: > > Taking exception 18 [v7M INVSTATE UsageFault] > ...BusFault with BFSR.STKERR > ...taking pending nonsecure exception 3 > qemu: fatal: Lockup: can't take terminal

Re: Exception return

If I won't make that change it gives me immediate error as follows: Taking exception 18 [v7M INVSTATE UsageFault] ...BusFault with BFSR.STKERR ...taking pending nonsecure exception 3 qemu: fatal: Lockup: can't take terminal derived exception (original exception priority -1) BR. Abhijeet. On

Re: Exception return

I made some changes to the code in qemu : https://github.com/qemu/qemu/blob/stable-6.0/target/arm/cpu.c#L339 . I have commented out the variable vecbase and directly given the address of my vector address(not zero) or where they are located in our binary file. Is that a problem? BR. Abhijeet. On

Re: Exception return

On Thu, 16 Dec 2021 at 17:44, Philippe Mathieu-Daudé wrote: > > Cc'ing qemu-arm developers. > > On 12/16/21 18:31, abhijeet inamdar wrote: > > Hi, > > > > I was running my .elf file on my custom machine(CM3) and was hit with > > this error when debugging and had the required -d flags and single

Re: Exception return

Cc'ing qemu-arm developers. On 12/16/21 18:31, abhijeet inamdar wrote: > Hi, > > I was running my .elf file on my custom machine(CM3) and was hit with > this error when debugging and had the required -d flags and single stepping. > > IN: Hal_MemFault > 0x7004e794:  4770       bx       lr > >

Re: Exception return

What might be the problem? or reasons for this error? BR. Abhijeet. On Thu, 16 Dec, 2021, 18:31 abhijeet inamdar, wrote: > Hi, > > I was running my .elf file on my custom machine(CM3) and was hit with this > error when debugging and had the required -d flags and single stepping. > > IN:

Exception return

Hi, I was running my .elf file on my custom machine(CM3) and was hit with this error when debugging and had the required -d flags and single stepping. IN: Hal_MemFault 0x7004e794: 4770 bx lr Trace 0: 0x7f4faa471100 [/7004e794/0x312000c1] Hal_MemFault R00=7004938d

qemu-img check fills terminal buffer with Leaked cluster 12345678 refcount=3 reference=2

Dear qemu experts, I recently ran qemu-img check on a large .qcow2 file, and got thousands (maybe millions) of output lines of the form:     Leaked cluster 12345678 refcount=3 reference=2 This seems like a bug in qemu-img check code, as repeating the same message for every cluster in a huge