search

dotnet / runtime

.NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
https://docs.microsoft.com/dotnet/core/
MIT License
15.26k stars 4.73k forks source link

/build/gdb-Dh0pdX/gdb-12.1/gdb/jit.c:1252: internal-error: jit_event_handler: Assertion `jiter->jiter_data != nullptr' failed. #104413

Open cshung opened 4 months ago

cshung commented 4 months ago

Description

GDB is outputting this error when debugging hello world.

/build/gdb-Dh0pdX/gdb-12.1/gdb/jit.c:1252: internal-error: jit_event_handler: Assertion `jiter->jiter_data != nullptr' failed.

Reproduction Steps

Expected behavior

We should be able to debug the application, looking at managed call stacks

Actual behavior

GDB reported an error like this and quit

/build/gdb-Dh0pdX/gdb-12.1/gdb/jit.c:1252: internal-error: jit_event_handler: Assertion `jiter->jiter_data != nullptr' failed.

Regression?

Likely, presumably it used to be working? But I have no idea when is the last known good.

Known Workarounds

No, if I need to debug using GDB, there is no way around this as far as I know. Of course I can use a different debugger.

Configuration

WSL, x64, on this commit 6b3f0f851da69c8c9f5c4df578d4b98fb4138a57

Other information

No response

dotnet-policy-service[bot] commented 4 months ago

Tagging subscribers to this area: @tommcdon See info in area-owners.md if you want to be subscribed.

janvorli commented 4 months ago

@cshung this stuff was added by Samsung folks long time ago for their internal needs, I am not sure if it is still in use. We never test it.

cshung commented 4 months ago

@kbaladurin

kbaladurin commented 4 months ago

We used gdbjit mainly with lldb, so it can not work properly with gdb (although at some point of time it worked if I remember correctly).

cc @gbalykov