All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
* Alsa Lib segfaults when built statically
       [not found] <1693793297749796867-webhooks-bot@alsa-project.org>
@ 2023-09-04  2:08 ` GitHub issues - opened
  0 siblings, 0 replies; 6+ messages in thread
From: GitHub issues - opened @ 2023-09-04  2:08 UTC (permalink / raw
  To: alsa-devel

alsa-project/alsa-lib issue #349 was opened from cybersoulK:

I building a game that uses alsa for linux. All of my linux players executables segfault.
Alsa Lib is built statically on a ubuntu machine with the following commands:

```
git clone https://github.com/alsa-project/alsa-lib
cd alsa-lib

apt-get update
apt-get install libtool
apt-get install make
apt install autoconf

autoreconf -i
./configure --disable-shared
make
```

Then i use libasound.a to build my Rust executable (On my mac machine).

I do the same process to build openssl for linux and it works great.


So There definitely is an issue when building alsa lib statically.

One of my players was able to provide me with a core dump that might be helpful to track the fault:

<img width="770" alt="image" src="https://github.com/alsa-project/alsa-lib/assets/102260392/7390b851-47a1-4e50-a33b-e33254dddabc">

[coredump.txt](https://github.com/alsa-project/alsa-lib/files/12508784/coredump.txt)

Issue URL     : https://github.com/alsa-project/alsa-lib/issues/349
Repository URL: https://github.com/alsa-project/alsa-lib

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Alsa Lib segfaults when built statically
       [not found] <1693793353928653240-webhooks-bot@alsa-project.org>
@ 2023-09-04  2:09 ` GitHub issues - edited
  0 siblings, 0 replies; 6+ messages in thread
From: GitHub issues - edited @ 2023-09-04  2:09 UTC (permalink / raw
  To: alsa-devel

alsa-project/alsa-lib issue #349 was edited from cybersoulK:

I am building a game that uses alsa. All of my linux players executables segfault.
Alsa Lib is built statically on a ubuntu machine with the following commands:

```
git clone https://github.com/alsa-project/alsa-lib
cd alsa-lib

apt-get update
apt-get install libtool
apt-get install make
apt install autoconf

autoreconf -i
./configure --disable-shared
make
```

Then i use libasound.a to build my Rust executable (On my mac machine).

I do the same process to build openssl for linux and it works great.


So There definitely is an issue when building alsa lib statically.

One of my players was able to provide me with a core dump that might be helpful to track the fault:

<img width="770" alt="image" src="https://github.com/alsa-project/alsa-lib/assets/102260392/7390b851-47a1-4e50-a33b-e33254dddabc">

[coredump.txt](https://github.com/alsa-project/alsa-lib/files/12508784/coredump.txt)

Issue URL     : https://github.com/alsa-project/alsa-lib/issues/349
Repository URL: https://github.com/alsa-project/alsa-lib

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Alsa Lib segfaults when built statically
       [not found] <1693793360123435974-webhooks-bot@alsa-project.org>
@ 2023-09-04  2:09 ` GitHub issues - edited
  0 siblings, 0 replies; 6+ messages in thread
From: GitHub issues - edited @ 2023-09-04  2:09 UTC (permalink / raw
  To: alsa-devel

alsa-project/alsa-lib issue #349 was edited from cybersoulK:

I am building a game that uses alsa. All of my linux players segfault.
Alsa Lib is built statically on a ubuntu machine with the following commands:

```
git clone https://github.com/alsa-project/alsa-lib
cd alsa-lib

apt-get update
apt-get install libtool
apt-get install make
apt install autoconf

autoreconf -i
./configure --disable-shared
make
```

Then i use libasound.a to build my Rust executable (On my mac machine).

I do the same process to build openssl for linux and it works great.


So There definitely is an issue when building alsa lib statically.

One of my players was able to provide me with a core dump that might be helpful to track the fault:

<img width="770" alt="image" src="https://github.com/alsa-project/alsa-lib/assets/102260392/7390b851-47a1-4e50-a33b-e33254dddabc">

[coredump.txt](https://github.com/alsa-project/alsa-lib/files/12508784/coredump.txt)

Issue URL     : https://github.com/alsa-project/alsa-lib/issues/349
Repository URL: https://github.com/alsa-project/alsa-lib

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Alsa Lib segfaults when built statically
       [not found] <1693793413935459614-webhooks-bot@alsa-project.org>
@ 2023-09-04  2:10 ` GitHub issues - edited
  0 siblings, 0 replies; 6+ messages in thread
From: GitHub issues - edited @ 2023-09-04  2:10 UTC (permalink / raw
  To: alsa-devel

alsa-project/alsa-lib issue #349 was edited from cybersoulK:

I am building a game that uses alsa. All of my linux players segfault. This has been going for over 1 year.
Alsa-lib is built statically on a ubuntu machine with the following commands:

```
git clone https://github.com/alsa-project/alsa-lib
cd alsa-lib

apt-get update
apt-get install libtool
apt-get install make
apt install autoconf

autoreconf -i
./configure --disable-shared
make
```

Then i use libasound.a to build my Rust executable (On my mac machine).

I do the same process to build openssl for linux and it works great.


So There definitely is an issue when building alsa lib statically.

One of my players was able to provide me with a core dump that might be helpful to track the fault:

<img width="770" alt="image" src="https://github.com/alsa-project/alsa-lib/assets/102260392/7390b851-47a1-4e50-a33b-e33254dddabc">

[coredump.txt](https://github.com/alsa-project/alsa-lib/files/12508784/coredump.txt)

Issue URL     : https://github.com/alsa-project/alsa-lib/issues/349
Repository URL: https://github.com/alsa-project/alsa-lib

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Alsa Lib segfaults when built statically
       [not found] <1693793584749669313-webhooks-bot@alsa-project.org>
@ 2023-09-04  2:13 ` GitHub issues - edited
  0 siblings, 0 replies; 6+ messages in thread
From: GitHub issues - edited @ 2023-09-04  2:13 UTC (permalink / raw
  To: alsa-devel

alsa-project/alsa-lib issue #349 was edited from cybersoulK:

I am building a game that uses alsa. All of my linux players segfault. This has been going for over 1 year.
Alsa-lib is built statically on a ubuntu machine with the following commands:

```
git clone https://github.com/alsa-project/alsa-lib
cd alsa-lib

apt-get update
apt-get install libtool
apt-get install make
apt install autoconf

autoreconf -i
./configure --disable-shared
make
```

Then i use libasound.a to build my Rust executable (On my mac machine).

I do the same process to build openssl for linux and it works great.


So There definitely is an issue when building alsa lib statically.

One of my players was able to provide me with a core dump that might be helpful to track down the fault:

<img width="770" alt="image" src="https://github.com/alsa-project/alsa-lib/assets/102260392/7390b851-47a1-4e50-a33b-e33254dddabc">

[coredump.txt](https://github.com/alsa-project/alsa-lib/files/12508784/coredump.txt)

Issue URL     : https://github.com/alsa-project/alsa-lib/issues/349
Repository URL: https://github.com/alsa-project/alsa-lib

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Alsa Lib segfaults when built statically
       [not found] <1693896328932979107-webhooks-bot@alsa-project.org>
@ 2023-09-05  6:45 ` GitHub issues - reopened
  0 siblings, 0 replies; 6+ messages in thread
From: GitHub issues - reopened @ 2023-09-05  6:45 UTC (permalink / raw
  To: alsa-devel

alsa-project/alsa-lib issue #349 was reopened from cybersoulK:

I am building a game that uses alsa. All of my linux players segfault. This has been going for over 1 year.
Alsa-lib is built statically on a ubuntu machine with the following commands:

```
git clone https://github.com/alsa-project/alsa-lib
cd alsa-lib

apt-get update
apt-get install libtool
apt-get install make
apt install autoconf

autoreconf -i
./configure --disable-shared
make
```

Then i use libasound.a to build my Rust executable (On my mac machine).

I do the same process to build openssl for linux and it works great.


So There definitely is an issue when building alsa lib statically.

One of my players was able to provide me with a core dump that might be helpful to track down the fault:

<img width="770" alt="image" src="https://github.com/alsa-project/alsa-lib/assets/102260392/7390b851-47a1-4e50-a33b-e33254dddabc">

[coredump.txt](https://github.com/alsa-project/alsa-lib/files/12508784/coredump.txt)

Issue URL     : https://github.com/alsa-project/alsa-lib/issues/349
Repository URL: https://github.com/alsa-project/alsa-lib

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2023-09-05  6:47 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <1693793297749796867-webhooks-bot@alsa-project.org>
2023-09-04  2:08 ` Alsa Lib segfaults when built statically GitHub issues - opened
     [not found] <1693793353928653240-webhooks-bot@alsa-project.org>
2023-09-04  2:09 ` GitHub issues - edited
     [not found] <1693793360123435974-webhooks-bot@alsa-project.org>
2023-09-04  2:09 ` GitHub issues - edited
     [not found] <1693793413935459614-webhooks-bot@alsa-project.org>
2023-09-04  2:10 ` GitHub issues - edited
     [not found] <1693793584749669313-webhooks-bot@alsa-project.org>
2023-09-04  2:13 ` GitHub issues - edited
     [not found] <1693896328932979107-webhooks-bot@alsa-project.org>
2023-09-05  6:45 ` GitHub issues - reopened

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.