Hello,
I have recently began looking at Genode for a project I am working on and I am having trouble with running the GDB run scripts. So far I have experimented with the following three:
- monitor - monitor_gdb - monitor_gdb_interactive
NOTE The command that I used to run is the following: make -C build/x86_64 run/<run script> KERNEL=hw BOARD=pc
The monitor script runs successfully. However, the monitor_gdb script crashes soon after launch with the warning that too many hardware breakpoints have already been set (see corresponding log below) . The monitor_gdb_interactive script launches a terminal for a brief second, however it too crashes (I presume it is the same error as with the monitor_gdb script). I have attached the corresponding log files below.
I have not altered any of the run scripts. The only changes I made were to the build/x86_64/etc/build.conf file which I have attached below.
I would also like to mention that I tried to run: make -C build/x86_64 run/<run script> KERNEL=linux BOARD=linux
but it also failed (see log below).
Any help will be greatly appreciated!
Kind regards, Rumen Mitov
Hi Rumen,
I could reproduce the problem with the published 23.05 binary tool chain, but it works for me with a more recent version built from source with the 'tool/tool_chain' script, which includes some GDB fixes added since 23.05. Could you give that a try?
Christian
On 04.07.24 11:11, Rumen Mitov via users wrote:
Hello,
I have recently began looking at Genode for a project I am working on and I am having trouble with running the GDB run scripts. So far I have experimented with the following three:
- monitor
- monitor_gdb
- monitor_gdb_interactive
*NOTE* The command that I used to run is the following: | make -C build/x86_64 run/<run script> KERNEL=hw BOARD=pc|
The |monitor| script runs successfully. However, the |monitor_gdb| script crashes soon after launch with the warning that too many hardware breakpoints have already been set (see corresponding log below) . The |monitor_gdb_interactive| script launches a terminal for a brief second, however it too crashes (I presume it is the same error as with the |monitor_gdb| script). I have attached the corresponding log files below.
I have not altered any of the run scripts. The only changes I made were to the |build/x86_64/etc/build.conf| file which I have attached below.
I would also like to mention that I tried to run: | |make -C build/x86_64 run/<run script> KERNEL=linux BOARD=linux||
but it also failed (see log below).
Any help will be greatly appreciated!
Kind regards, Rumen Mitov
users mailing list -- users@lists.genode.org To unsubscribe send an email to users-leave@lists.genode.org Archived at https://lists.genode.org/mailman3/hyperkitty/list/users@lists.genode.org/mes...
Hi Christian,
Thank you for the tip. I got monitor_gdb to run successfully but the terminal spawned by the monitor_gdb_interactive still crashes instantly. I tried running monitor_gdb_interactive in the background and connecting to it via gdb with target remote :5555. Unfortunately this was unsuccessful and I got the error "Remote refused setting all-stop mode with: E01". According to [this](https://stackoverflow.com/questions/39692161/gdb-remote-debugging-fails-with...) post, it seems that the gdb version is not mismatched with the remote. When running gdb I did so with the /usr/local/genode/tool/23.05/bin/genode-x86-gdb and /usr/local/genode/tool/current/bin/genode-x86-gdb commands (which were both version 13.1). I could not find any information regarding the version that Genode uses for the backend, so any insights regarding that will be very helpful!https://stackoverflow.com/questions/39692161/gdb-remote-debugging-fails-with...
Kind regards, Rumen On Thursday, July 4th, 2024 at 4:59 PM, Christian Prochaska christian.prochaska@genode-labs.com wrote:
Hi Rumen,
I could reproduce the problem with the published 23.05 binary tool chain, but it works for me with a more recent version built from source with the 'tool/tool_chain' script, which includes some GDB fixes added since 23.05. Could you give that a try?
Christian
On 04.07.24 11:11, Rumen Mitov via users wrote:
Hello,
I have recently began looking at Genode for a project I am working on and I am having trouble with running the GDB run scripts. So far I have experimented with the following three:
- monitor
- monitor_gdb
- monitor_gdb_interactive
NOTE The command that I used to run is the following: make -C build/x86_64 run/<run script> KERNEL=hw BOARD=pc
The monitor script runs successfully. However, the monitor_gdb script crashes soon after launch with the warning that too many hardware breakpoints have already been set (see corresponding log below) . The monitor_gdb_interactive script launches a terminal for a brief second, however it too crashes (I presume it is the same error as with the monitor_gdb script). I have attached the corresponding log files below.
I have not altered any of the run scripts. The only changes I made were to the build/x86_64/etc/build.conf file which I have attached below.
I would also like to mention that I tried to run: make -C build/x86_64 run/<run script> KERNEL=linux BOARD=linux
but it also failed (see log below).
Any help will be greatly appreciated!
Kind regards, Rumen Mitov
users mailing list -- users@lists.genode.org To unsubscribe send an email to users-leave@lists.genode.org Archived at https://lists.genode.org/mailman3/hyperkitty/list/users@lists.genode.org/mes...
Hi Rumen,
the debug monitor only supports GDB's non-stop mode, which needs to be set before connecting. You can find the relevant command line arguments for genode-x86-gdb in the 'monitor_gdb_interactive.run' file.
Christian
On 04.07.24 23:18, Rumen Mitov via users wrote:
Hi Christian,
Thank you for the tip. I got |monitor_gdb| to run successfully but the termin|al spawned by the monitor_gdb_interactive| still crashes instantly. I tried running |monitor_gdb_interactive| in the background and connecting to it via gdb with |target remote :5555|.
Unfortunately this was unsuccessful and I got the error|"Remote refused setting all-stop mode with: E01". According to this https://stackoverflow.com/questions/39692161/gdb-remote-debugging-fails-with-error-e01 post, it seems that the gdb version is not mismatched with the remote. When running gdb I did so with the |/usr/local/genode/tool/23.05/bin/genode-x86-gdb| and |/usr/local/genode/tool/current/bin/genode-x86-gdb| commands (which were both version 13.1). I could not find any information regarding the version that Genode uses for the backend, so any insights regarding that will be very helpful! https://stackoverflow.com/questions/39692161/gdb-remote-debugging-fails-with-error-e01| || Kind regards, Rumen On Thursday, July 4th, 2024 at 4:59 PM, Christian Prochaska christian.prochaska@genode-labs.com wrote:
Hi Rumen,
I could reproduce the problem with the published 23.05 binary tool chain, but it works for me with a more recent version built from source with the 'tool/tool_chain' script, which includes some GDB fixes added since 23.05. Could you give that a try?
Christian
On 04.07.24 11:11, Rumen Mitov via users wrote:
Hello,
I have recently began looking at Genode for a project I am working on and I am having trouble with running the GDB run scripts. So far I have experimented with the following three:
- monitor
- monitor_gdb
- monitor_gdb_interactive
*NOTE* The command that I used to run is the following: |make -C build/x86_64 run/<run script> KERNEL=hw BOARD=pc|
The |monitor| script runs successfully. However, the |monitor_gdb| script crashes soon after launch with the warning that too many hardware breakpoints have already been set (see corresponding log below) . The |monitor_gdb_interactive| script launches a terminal for a brief second, however it too crashes (I presume it is the same error as with the |monitor_gdb| script). I have attached the corresponding log files below.
I have not altered any of the run scripts. The only changes I made were to the |build/x86_64/etc/build.conf| file which I have attached below.
I would also like to mention that I tried to run: ||make -C build/x86_64 run/<run script> KERNEL=linux BOARD=linux||
but it also failed (see log below).
Any help will be greatly appreciated!
Kind regards, Rumen Mitov
users mailing list -- users@lists.genode.org To unsubscribe send an email to users-leave@lists.genode.org Archived at https://lists.genode.org/mailman3/hyperkitty/list/users@lists.genode.org/mes...
users mailing list -- users@lists.genode.org To unsubscribe send an email to users-leave@lists.genode.org Archived at https://lists.genode.org/mailman3/hyperkitty/list/users@lists.genode.org/mes...
-
Christian Prochaska -
Rumen Mitov