-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Attempting to create a Homa server results in a Segmentation Fault #15
Comments
Sorry for my slow response. What version of gRPC are you working with? |
No worries, thank you for helping! I am using gRPC 1.57.0 with the most recent version of the Homa Kernel Module running on top of Ubuntu 22.04 LTS with Linux kernel version 6.1.38. |
I just tried running test_server on my sources (same versions of everything
as you) and it seems to start up fine for me.
Could you compile with debugging (set "DEBUG := yes" in the Makefile), run
test_server under gdb, then when it crashes type "where" and send me the
gdb output?
…On Tue, Jun 18, 2024 at 10:10 AM Chase Webb ***@***.***> wrote:
No worries, thank you for helping! I am using gRPC 1.57.0 with the most
recent version of the Homa Kernel Module running on top of Ubuntu 22.04 LTS
with Linux kernel version 6.1.38.
—
Reply to this email directly, view it on GitHub
<#15 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACOOUCRRQ6OFYAKLVNQRPBTZIBSZRAVCNFSM6AAAAABJE5YF3GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZWGU4DQNJWGM>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
After setting DEBUG to yes in the Makefile, there was no segmentation fault. However, the problem persists when compiling with DEBUG set to no. |
Well that's a bummer! This may be hard to debug...
How about running it under gdb when compiled with DEBUG off and send me a
stack trace of the crash? Perhaps that will yield some clues.
…On Thu, Jun 20, 2024 at 12:20 PM Chase Webb ***@***.***> wrote:
After setting DEBUG to yes in the Makefile, there was no segmentation
fault. However, the problem persists when compiling with DEBUG set to no.
—
Reply to this email directly, view it on GitHub
<#15 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACOOUCQTQVRSDKFMCE7RZV3ZIMTPLAVCNFSM6AAAAABJE5YF3GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBRGM3TAOJUGI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Sorry for delay. Here is the stack trace using gdb
|
Thanks for the stack trace (I recently noticed that you already sent this earlier... sorry for making you send it again). It appears that the channel arguments object is somehow getting corrupted. Can you try the following steps?
Hopefully this will help to narrow down the problem a bit. |
Sorry for my late response. I am not able to compile with the new homa_listener. I get the following output:
|
That's strange; I see the method's definition in the file
src/core/lib/channel/channel_args.cc in the grpc directory. Can you (a) see
if there is such a method defined in your version of the file and (b)
double-check the version of gRPC that you are using (I'm using 1.57.0)?
Could you respond back here with the git commit # from which you are
compiling your gRPC sources?
Thanks.
…-John-
On Tue, Jul 16, 2024 at 1:45 PM Chase Webb ***@***.***> wrote:
Sorry for my late response. I am not able to compile with the new
homa_listener. I get the following output:
`
homa_listener.cc: In member function ‘void
HomaListener::Transport::start(grpc_core::Server*, const
std::vector<grpc_pollset*>*)’:
homa_listener.cc:297:28: error: ‘const class grpc_core::ChannelArgs’ has
no member named ‘printNames’
297 | server->channel_args().printNames();
| ^~~~~~~~~~
`
—
Reply to this email directly, view it on GitHub
<#15 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACOOUCVJS4OUQDEGXUQOUCLZMWA77AVCNFSM6AAAAABJE5YF3GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZRG44TQNBYGQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I was not able to find the method when searching through the file. I was able to determine that I am using gRPC 1.57.0 and issuing git log resulted in this commit number:
|
Oops, sorry, my goof. In looking through my sources I see that I added that method myself for debugging a while ago, but forgot. I'm attaching my version of src/core/lib/channel/channel_args.cc (I had to attach it as a .txt file instead of .cc so that GitHub would let it pass); can you drop that into your grpc tree and build with that to run the test? |
I also had to make a change to the appropriate header file to add a declaration of printNames(). After doing so and running test_server I am not receiving any output before the segmentation fault. I am not sure if this is a mistake on my end in configuring it or something else. |
After another attempt, the code does not segfault when using the provided channel_args. The output of running test_server is as follows:
|
Just double-checking to make sure I understand: the run above (which did not segfault) occurred even when running without debugging? If not, can you run it without debugging? |
Yes, the above output is the result from using the provided files and compiling and running without debugging. |
Executing test_server results in a segmentation fault created in the execution of the BuildAndStart() method. Below is the stack backtrace produced by GDB.
The text was updated successfully, but these errors were encountered: