Skip to content
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

Broken Pipe Exception and no PDB available #94

Closed
fmuntean opened this issue Sep 29, 2019 · 5 comments
Closed

Broken Pipe Exception and no PDB available #94

fmuntean opened this issue Sep 29, 2019 · 5 comments

Comments

@fmuntean
Copy link

fmuntean commented Sep 29, 2019

ld-musl-armhf.so.pdb contains the debug information required to find the source for the module ld-musl-armhf.so.1

I keep getting broken pipe exception in visual Studio while using TCP socket and the PDB does not seems to be available. The stack trace also does not show any user code only : ld-musl-armhf.so.1![Unknown/Just-In-Time compiled code]

@richardtaylorrt
Copy link
Contributor

Hi - please could provide some more details of how to hit this problem. Can you paste full output from Visual studio debug output? Can you share example code that illustrates this? Does it happen immediately, or only ocassionally or after some time? Thanks.

@fmuntean
Copy link
Author

fmuntean commented Oct 1, 2019

The way I got this problem was to get a client TCP socket connect to a server and try to receive data on it. As the socket was blocking and no data was received it timed out thus the error. As I mentioned there was nothing on the debug that I could get you other that what I mentioned above.
Can you point me to the pdb file for the above mentioned library? I could not find any pdb in the SDK folder.

@richardtaylorrt
Copy link
Contributor

Thanks for the extra information. We'll look into this further.

@richardtaylorrt
Copy link
Contributor

Hi - we don't currently supply debug symbols for the runtime libraries.

Is the socket timeout unexpected? Did you expect different behavior from the runtime? (If so, please tell us what you expected.) Are you able to write signal handling code for this?

When the signal occurs, you should be able to go to the 'Threads' window and switch to the main thread to see your app's stack.

@fmuntean
Copy link
Author

fmuntean commented Oct 4, 2019

Thanks for clarification on the debug symbols for the runtime libs.
I was able to get around the socket timeout.

@fmuntean fmuntean closed this as completed Oct 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants