Skip to content
This repository has been archived by the owner on Feb 5, 2023. It is now read-only.

Pulseaudio daemon segfaults on arm #3

Open
xavier83 opened this issue Jun 21, 2016 · 5 comments
Open

Pulseaudio daemon segfaults on arm #3

xavier83 opened this issue Jun 21, 2016 · 5 comments

Comments

@xavier83
Copy link

pulseaudio was build using this build.sh and the segfault log is here

@glance-
Copy link
Owner

glance- commented Jun 22, 2016

I don't have a test case for running the code on actual hardware anymore. Publish one and ill take it for a spin with my binaries.

@xavier83
Copy link
Author

I have created a demo app here MyPulseAudio .
The segfault happens when you press the play button in the app.

@glance-
Copy link
Owner

glance- commented Jun 26, 2016

Running pulse audio on the main thread will get you in to lots of trouble. I'd say clobber up something based on https://github.com/jackpal/Android-Terminal-Emulator like how @joeyh did with git annex assistant, and you will evade lots of pitfalls.

Anyhow. Last time i did some real testing i used a rooted phone and su'ed into a app with approperiate permissions and launched pulseaudio by hand. Then I used module-native-protocol-tcp to create a loop sending audio from my laptop to my phone and back via wifi, just as a simple smoke test. I'd suggest you do the same to exclude any problems with your app.

@xavier83
Copy link
Author

I should try running it on the main thread as you suggested. thanks for the pointer.

Anyhow. Last time i did some real testing i used a rooted phone and su'ed into a app with approperiate permissions and launched pulseaudio by hand

Actually that was my first attempt too, it still segfaulted. could be something to do with the -pie linker flag (export LDFLAGS=-pie in build.sh). I added this because it was mandated by android 5.0 , got error: only position independent executables (PIE) are supported.. a tombstone log got created, i've attached it here if it would be of any help. not sure how to add more info to the log though. Thought of running ndk-stack, but I think it'll only work with ndk-build style ports.

@glance-
Copy link
Owner

glance- commented Jun 29, 2016

Hmm.. Rebuild pa with -g in your CFLAGS and LDFLAGS and we will probably get a stacktrace which will explain where it tries to follow a null pointer.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants