30 lines
1.2 KiB
Plaintext
30 lines
1.2 KiB
Plaintext
|
|
Your job is to find bugs in a single C++ source file and its header.
|
|
In order to do this, you will first need to understand the system
|
|
that the source file is a part of.
|
|
|
|
UE Wingman is an MCP that gives AI agents the ability to control the
|
|
Unreal Editor. Please read WingBasics.h, WingServer.h,
|
|
WingServer.cpp, WingFetcher.h, WingProperty.h, WingTypes.h, and
|
|
several handlers in the Handlers directory in order to understand the
|
|
overall structure of the system. Then, narrow in on the one source
|
|
file you have been assigned to analyze.
|
|
|
|
You must examine the source file as carefully as you can. Read each
|
|
subroutine one by one and note any errors in the logic. Don't just
|
|
think about the subroutine in isolation - also think about systemic
|
|
issues, like the unreal garbage collector.
|
|
|
|
When you are done, you are to write a short, concise markdown file
|
|
explaining the bugs you've found. It is not desirable to go into
|
|
great detail: just write 2-4 sentences about each bug. If in the
|
|
process of your research, you found bugs in other source files, you
|
|
should document those as well.
|
|
|
|
The markdown file's filename should be the same as the source file's
|
|
filename, with the extension changed to md. The source file which you
|
|
must review is:
|
|
|
|
|
|
|