Re:‏ ‏ Crash in memory_region_init_ram call chain, when --bios command line parameter is presented.

2023-02-19 Thread Alyosha Shevandin
Maydell ‏‏נשלח: יום שלישי 14 פברואר 2023 16:17 ‏‏אל: Alyosha Shevandin עותק: qemu-discuss@nongnu.org ‏‏נושא: Re: ‏ Crash in memory_region_init_ram call chain, when --bios command line parameter is presented. On Tue, 14 Feb 2023 at 11:54, Alyosha Shevandin wrote: > > Thank you for your ans

Re: ‏ Crash in memory_region_init_ram call chain, when --bios command line parameter is presented.

2023-02-14 Thread Peter Maydell
On Tue, 14 Feb 2023 at 11:54, Alyosha Shevandin wrote: > > Thank you for your answer. I belive that 'owner' parameter is initialized: 1) > without --bios parameter the code does not crash; 2) I check the the owner > parameter before; > Here is the fragment of my code: > > static void my_soc_ini

Crash in memory_region_init_ram call chain, when --bios command line parameter is presented.

2023-02-14 Thread Alyosha Shevandin
I would appreciate any clue about the crash. When I start my custom SoC emulation and the –bios command line parameter us presented, the QEMU processes crashes before the custom code even tries to load the firmware. It crashes in the *memory_region_init_ram* call chain with the follow stack:

Re:‏ Crash in memory_region_init_ram call chain, when --bios command line parameter is presented.

2023-02-14 Thread Alyosha Shevandin
in עותק: qemu-discuss@nongnu.org ‏‏נושא: Re: Crash in memory_region_init_ram call chain, when --bios command line parameter is presented. On Tue, 14 Feb 2023 at 11:03, Alyosha Shevandin wrote: > > > I would appreciate any clue about the crash. > > When I start my custom SoC emulat

Re: Crash in memory_region_init_ram call chain, when --bios command line parameter is presented.

2023-02-14 Thread Peter Maydell
On Tue, 14 Feb 2023 at 11:03, Alyosha Shevandin wrote: > > > I would appreciate any clue about the crash. > > When I start my custom SoC emulation and the –bios command line parameter us > presented, the QEMU processes crashes before the custom code even tries to > load the firmware. It crashes