29 May
2012
29 May
'12
9:05 a.m.
Since a few weeks I have issues with jack2 on Arch
1. It's gone pretty verbose, filling any terminal from where a jack
application was started with lots of messages. These mingle with
the client's output, rendering it more or less unreadable.
Neither --silent nor the --verbose flag change the amount of jack's
output.
2. It behaves as if the -T (--temporary) flag where given, i.e. exits
once all clients have closed their connections.
Some example output, which is the result of jack2 started with
jackd -d alsa -d hw:0 -p 128 -n 3, then starting and quitting mplayer.
http://sebsauvage.net/paste/?6fd645cc70f83404#8NHeh0ASRuLREkgFbPBNMRi4M8C35…
Arch currently provides 1.9.8, but this seems unrelated to the version.
Downgrading to older jack versions or package releases does not fix
this, despite those having been perfectly fine at the time.
Compiling locally and experimenting with configure flags didn't help
either.
Searching the web&Arch fora brought nothing up,
so here I am, asking for help.
best,
david
29 May
29 May
10:48 a.m.
On 05/28/2012 09:05 PM, David Adler wrote:
Since a few weeks I have issues with jack2 on Arch
1. It's gone pretty verbose, filling any terminal from where a jack
application was started with lots of messages. These mingle with
the client's output, rendering it more or less unreadable.
Neither --silent nor the --verbose flag change the amount of jack's
output.
2. It behaves as if the -T (--temporary) flag where given, i.e. exits
once all clients have closed their connections.
Some example output, which is the result of jack2 started with
jackd -d alsa -d hw:0 -p 128 -n 3, then starting and quitting mplayer.
http://sebsauvage.net/paste/?6fd645cc70f83404#8NHeh0ASRuLREkgFbPBNMRi4M8C35…
Arch currently provides 1.9.8, but this seems unrelated to the version.
Downgrading to older jack versions or package releases does not fix
this, despite those having been perfectly fine at the time.
Hmmm. I have jackd2 v 1.9.8~dfsg.3+20120418gitf82ec715-6 from Sid
running here on Aptosid (Debian Sid) without any problems.
Is there some hidden config or .desktop or .local file somewhere that
could be effecting it?
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
http://clanjones.org/david/
http://dancing-treefrog.deviantart.com/
2 p.m.
On Tue, May 29, 2012 at 10:48 AM, david wrote:
Hmmm. I have jackd2 v 1.9.8~dfsg.3+20120418gitf82ec715-6 from Sid running
here on Aptosid (Debian Sid) without any problems.
Is there some hidden config or .desktop or .local file somewhere that could
be effecting it?
there is ~/.jackdrc, belonging to qjackctl if I'm not mistaken.
Nothing else, nothing in /etc. I'm starting jack from the command
line, so it shouldn't(?) matter anyway. Jack1 behaves a usual.
Arch ships a mixed --classic --dbus build, changing that to
pure --classic also makes no difference.
I might as well just use jack1, but then issues pop up with syncing
ardour and seq24 (which is probably seq24's fault, not jack's)
This leaves me with jack2.
thnx&cheers,
david
2:06 p.m.
On 05/29/12 14:00, David Adler wrote:
I might as well just use jack1, but then issues pop up
with syncing
ardour and seq24 (which is probably seq24's fault, not jack's)
Hello David,
You might want to try seq24 from the Launchpad development (bazaar)
branch. It contains a hack/fix to make seq24 work with
jack1 > 0.118.x again.
Best,
Jeremy
2:55 p.m.
On Tue, May 29, 2012 at 2:05 PM, Jeremy Jongepier wrote:
On 05/29/12 14:00, David Adler wrote:
Thanks Jeremy, indeed, when using the -bzr version, seq24 works with jack1.
I was aware of that version, but there are just so many combinations
to check :) (master/slave, jack1/jack2, bzr/tarball).
The downside of jack1 here is, that ardour regularly gives up with the
"Jack has either been shutdown or it disconnected Ardour because Ardour
was not fast enough..." message popping up.
But that's another topic I've not investigated yet, I'd rather be able to use
jack2 again, which used to work fairly well.
best,
david
I might as well just use jack1, but then issues pop up with syncing
ardour and seq24 (which is probably seq24's fault, not jack's)
Hello David,
You might want to try seq24 from the Launchpad development (bazaar) branch.
It contains a hack/fix to make seq24 work with
jack1 > 0.118.x again. 
2:59 p.m.
On 05/29/2012 02:00 PM, David Adler wrote:
On Tue, May 29, 2012 at 10:48 AM, david wrote:
jack2 uses ~/.config/jack/conf.xml
and ~/.log/jack/ -- though the latter might be dbus specific.
Hmmm. I have jackd2 v 1.9.8~dfsg.3+20120418gitf82ec715-6 from Sid running
here on Aptosid (Debian Sid) without any problems.
Is there some hidden config or .desktop or .local file somewhere that could
be effecting it?
there is ~/.jackdrc, belonging to qjackctl if I'm not mistaken.
Nothing else, nothing in /etc. I'm starting jack from the command
line, so it shouldn't(?) matter anyway. Jack1 behaves a usual. Arch ships a mixed --classic --dbus build, changing
that to
pure --classic also makes no difference.
I might as well just use jack1, but then issues pop up with syncing
ardour and seq24 (which is probably seq24's fault, not jack's)
This leaves me with jack2.
thnx&cheers,
david
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
3:29 p.m.
On Tue, May 29, 2012 at 2:59 PM, Robin Gareus wrote:
On 05/29/2012 02:00 PM, David Adler wrote:
I do have a ~/.config/jack/ directory, which is empty.
According to the last paragraph on
http://trac.jackaudio.org/wiki/JackDbusPackaging
this file is jackdbus only. So should I bother?
thnx.
On Tue, May 29, 2012 at 10:48 AM, david wrote:
jack2 uses ~/.config/jack/conf.xml
and ~/.log/jack/ -- though the latter might be dbus specific.
Hmmm. I have jackd2 v 1.9.8~dfsg.3+20120418gitf82ec715-6 from Sid running
here on Aptosid (Debian Sid) without any problems.
Is there some hidden config or .desktop or .local file somewhere that could
be effecting it?
there is ~/.jackdrc, belonging to qjackctl if I'm not mistaken.
Nothing else, nothing in /etc. I'm starting jack from the command
line, so it shouldn't(?) matter anyway. Jack1 behaves a usual. 
4:50 p.m.
On 2012-05-29 13:00, David Adler wrote:
there is ~/.jackdrc, belonging to qjackctl if I'm not mistaken.
Nothing else, nothing in /etc. I'm starting jack from the command
line, so it shouldn't(?) matter anyway. Jack1 behaves a usual.
~/.jackdrc does NOT belong to qjackctl. there's a qjacktl option to
update it, for courtesy :)
~/.jackdrc is the command line source (some call it configuration) for
the auto-start feature of jackd, when not currently up and running--it
belongs to jack itself; it might not be of any use or just irrelevant if
jackdbus is in charge though.
cheers
--
rncbc aka. Rui Nuno Capela
5:24 p.m.
On Tue, May 29, 2012 at 3:50 PM, rncbc wrote:
On 2012-05-29 13:00, David Adler wrote:
Thanks Rui. So am I right assuming that if I start classic jackd from the
command line, be it manually or from ~/.xinitrc, that there is no
configuration file that "gets in the way" in that case?
That's at least my experience from the past years, this used to work well.
cheers,
david
there is ~/.jackdrc, belonging to qjackctl if I'm not mistaken.
Nothing else, nothing in /etc. I'm starting jack from the command
line, so it shouldn't(?) matter anyway. Jack1 behaves a usual.
~/.jackdrc does NOT belong to qjackctl. there's a qjacktl option to update
it, for courtesy :)
~/.jackdrc is the command line source (some call it configuration) for the
auto-start feature of jackd, when not currently up and running--it belongs
to jack itself; it might not be of any use or just irrelevant if jackdbus is
in charge though. 
31 May
31 May
1:01 a.m.
On 29 May 2012 08:05, David Adler <david.jo.adler(a)gmail.com> wrote:
Since a few weeks I have issues with jack2 on Arch
1. It's gone pretty verbose, filling any terminal from where a jack
application was started with lots of messages. These mingle with
the client's output, rendering it more or less unreadable.
Neither --silent nor the --verbose flag change the amount of jack's
output.
2. It behaves as if the -T (--temporary) flag where given, i.e. exits
once all clients have closed their connections.
Some example output, which is the result of jack2 started with
jackd -d alsa -d hw:0 -p 128 -n 3, then starting and quitting mplayer.
http://sebsauvage.net/paste/?6fd645cc70f83404#8NHeh0ASRuLREkgFbPBNMRi4M8C35…
Arch currently provides 1.9.8, but this seems unrelated to the version.
Downgrading to older jack versions or package releases does not fix
this, despite those having been perfectly fine at the time.
Compiling locally and experimenting with configure flags didn't help
either.
Searching the web&Arch fora brought nothing up,
so here I am, asking for help.
best,
david
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
I have the same verbose behaviour problem with jack2 on Arch Linux 64 bit.
1 Jun
1 Jun
2:47 a.m.
Maybe we should start a forum thread or even file a bug report on Arch?
On 31 May 2012 00:58, David Adler <david.jo.adler(a)gmail.com> wrote:
On Thu, May 31, 2012 at 1:00 AM, mark hadman wrote:
I have the same verbose behaviour problem with
jack2 on Arch Linux 64 bit.
Thanks Mark, good to know I'm not the only one.
I have it on both, 64 and 32 bit.
best,
d
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
2:52 p.m.
On 05/31/2012 01:58 AM, David Adler wrote:
On Thu, May 31, 2012 at 1:00 AM, mark hadman wrote:
It might have to do with Arch's compiler[-flags] and how jack2 uses
unions .. or scoping: JackGlobals vs Engine-Parameters.. although I
don't have an explanation.. all seems good.
A hunch: it could be caused by using 'server_ptr->verbose.b' (a union)
as boolean. The sever only checks "if (server_ptr->verbose.b)". The
union itself comprises other uninitialized values that could make it
evaluate to true (though it shouldn't, but maybe some compiler
optimization casts it to (int) instead of (bool) )
I know this is the '-users' list (I'm ccing jack-devel), but could
someone who experiences the problem try to track it down?
Basically just add a few printf()'s. Start at: common/JackControlAPI.cpp
- line 926 - before the call to "new JackServer(..)" add
printf("DEBUG verbose:
%s\n",(server_ptr->verbose.b)?"on":"off");
recompile, launch jackd. If it prints "verbose: on", sth is wrong with
parameter initialization in main() or with using unions. If it's "off"
the problem sits deeper:
add a line just after common/JackServer.cpp line 66
printf("DEBUG verbose2:
%s\n",(JackGlobals::fVerbose)?"on":"off");
...
A crude test for the union() hunch would be to change
common/JackControlAPI.h line 53:
replace
"union jackctl_parameter_value"
with
"struct jackctl_parameter_value"
and compile with '-fpermissive' like this:
CXXFLAGS="-fpermissive" ./waf configure
./waf
..not sure if that'll work though..
HTH,
robin
I have the same verbose behaviour problem with
jack2 on Arch Linux 64 bit.
Thanks Mark, good to know I'm not the only one.
I have it on both, 64 and 32 bit.
best,
d
3:48 p.m.
New subject: [Jack-Devel] jack2 turned verbose
On Fri, Jun 1, 2012 at 2:52 PM, Robin Gareus wrote:
It might have to do with Arch's compiler[-flags] and how jack2 uses
unions .. or scoping: JackGlobals vs Engine-Parameters.. although I
don't have an explanation.. all seems good.
Compiler flags (for 32bit) are, (from unaltered /etc/makepkg.conf):
CXXFLAGS="-march=i686 -mtune=generic -O2 -pipe -fstack-protector
--param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2"
A hunch: it could be caused by using
'server_ptr->verbose.b' (a union)
as boolean. The sever only checks "if (server_ptr->verbose.b)". The
union itself comprises other uninitialized values that could make it
evaluate to true (though it shouldn't, but maybe some compiler
optimization casts it to (int) instead of (bool) )
I know this is the '-users' list (I'm ccing jack-devel), but could
someone who experiences the problem try to track it down?
Basically just add a few printf()'s. Start at: common/JackControlAPI.cpp
- line 926 - before the call to "new JackServer(..)" add
printf("DEBUG verbose:
%s\n",(server_ptr->verbose.b)?"on":"off");
recompile, launch jackd. If it prints "verbose: on", sth is wrong with
parameter initialization in main() or with using unions. If it's "off"
the problem sits deeper:
DEBUG verbose: on
add a line just after common/JackServer.cpp line 66
printf("DEBUG verbose2:
%s\n",(JackGlobals::fVerbose)?"on":"off");
...
above, your line number didn't match exactly, so we seem to have
different versions (1.9.7 here). Thus, I wasn't exactly sure where to
add the prinf() and did the following:
...
JackServerGlobals::fUserCount = 1; // One user
printf("DEBUG verbose2:
%s\n",(JackGlobals::fVerbose)?"on":"off");
JackGlobals::fVerbose = verbose;
printf("DEBUG verbose3:
%s\n",(JackGlobals::fVerbose)?"on":"off");
}
which prints:
DEBUG verbose2: off
DEBUG verbose3: on
A crude test for the union() hunch would be to change
common/JackControlAPI.h line 53:
replace
"union jackctl_parameter_value"
with
"struct jackctl_parameter_value"
and compile with '-fpermissive' like this:
CXXFLAGS="-fpermissive" ./waf configure
./waf
Again, mismatching line numbers. I assume you meant the line:
union jackctl_parameter_value verbose;
Changing that to struct fixes both issues I reported,
the verbose output and exit on last client close.
So we seem to be getting somewhere. Nice.
thanks Robin,
d
3:58 p.m.
New subject: [Jack-Devel] jack2 turned verbose
On Fri, Jun 1, 2012 at 3:48 PM, David Adler wrote:
On Fri, Jun 1, 2012 at 2:52 PM, Robin Gareus wrote:
(It was a little too late that I saw the square brackets around -flags.)
Compiler is gcc 4.7.0
It might have to do with Arch's compiler[-flags] and how jack2 uses
unions .. or scoping: JackGlobals vs Engine-Parameters.. although I
don't have an explanation.. all seems good.
Compiler flags (for 32bit) are, (from unaltered /etc/makepkg.conf):
CXXFLAGS="-march=i686 -mtune=generic -O2 -pipe -fstack-protector
--param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2"
3:58 p.m.
New subject: [Jack-Devel] jack2 turned verbose
Hi David,
On 06/01/2012 03:48 PM, David Adler wrote:
On Fri, Jun 1, 2012 at 2:52 PM, Robin Gareus wrote:
just a quick re: the line-numbers refered to git-head
https://github.com/jackaudio/jack2/
currently 007cdc37142a
It looks like it is indeed caused by using unions to check for /true/.
"if ([bool/int/..]union) -> always true"
But I'm at a loss what'd cause those issues and how to best fix it.
Maybe someone else can take it from here. It should be sufficient info
to file a bug report at https://github.com/jackaudio/jack2/issues
best,
robin
It might have to do with Arch's compiler[-flags] and how jack2 uses
unions .. or scoping: JackGlobals vs Engine-Parameters.. although I
don't have an explanation.. all seems good.
Compiler flags (for 32bit) are, (from unaltered /etc/makepkg.conf):
CXXFLAGS="-march=i686 -mtune=generic -O2 -pipe -fstack-protector
--param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2"
A hunch: it could be caused by using
'server_ptr->verbose.b' (a union)
as boolean. The sever only checks "if (server_ptr->verbose.b)". The
union itself comprises other uninitialized values that could make it
evaluate to true (though it shouldn't, but maybe some compiler
optimization casts it to (int) instead of (bool) )
I know this is the '-users' list (I'm ccing jack-devel), but could
someone who experiences the problem try to track it down?
Basically just add a few printf()'s. Start at: common/JackControlAPI.cpp
- line 926 - before the call to "new JackServer(..)" add
printf("DEBUG verbose:
%s\n",(server_ptr->verbose.b)?"on":"off");
recompile, launch jackd. If it prints "verbose: on", sth is wrong with
parameter initialization in main() or with using unions. If it's "off"
the problem sits deeper:
DEBUG verbose: on
add a line just after common/JackServer.cpp line
66
printf("DEBUG verbose2:
%s\n",(JackGlobals::fVerbose)?"on":"off");
...
above, your line number didn't match exactly, so we seem to have
different versions (1.9.7 here). Thus, I wasn't exactly sure where to
add the prinf() and did the following:
...
JackServerGlobals::fUserCount = 1; // One user
printf("DEBUG verbose2:
%s\n",(JackGlobals::fVerbose)?"on":"off");
JackGlobals::fVerbose = verbose;
printf("DEBUG verbose3:
%s\n",(JackGlobals::fVerbose)?"on":"off");
}
which prints:
DEBUG verbose2: off
DEBUG verbose3: on
A crude test for the union() hunch would be to
change
common/JackControlAPI.h line 53:
replace
"union jackctl_parameter_value"
with
"struct jackctl_parameter_value"
and compile with '-fpermissive' like this:
CXXFLAGS="-fpermissive" ./waf configure
./waf
Again, mismatching line numbers. I assume you meant the line:
union jackctl_parameter_value verbose;
Changing that to struct fixes both issues I reported,
the verbose output and exit on last client close.
So we seem to be getting somewhere. Nice.
thanks Robin,
d 
4 Jun
4 Jun
10:06 p.m.
New subject: [Jack-Devel] jack2 turned verbose
On 06/01/2012 03:58 PM, Robin Gareus wrote:
Hi David,
On 06/01/2012 03:48 PM, David Adler wrote:
I've had a closer look at this and this patch seems to be working for me
(their's no equivalent bool in jack_driver_param_value_t)
diff -Nurp '-x*~' jack-1.9.8.orig/common/JackControlAPI.cpp
jack-1.9.8/common/JackControlAPI.cpp
--- jack-1.9.8.orig/common/JackControlAPI.cpp 2011-12-19
12:54:02.000000000 +0100
+++ jack-1.9.8/common/JackControlAPI.cpp 2012-06-04 21:57:59.264581780 +0200
@@ -246,7 +246,7 @@ jackctl_add_driver_parameters(
break;
case JackDriverParamBool:
jackctl_type = JackParamBool;
- jackctl_value.b = descriptor_ptr->value.i;
+ jackctl_value.b = (descriptor_ptr->value.i > 0);
break;
default:
jack_error("unknown driver parameter type %i",
(int)descriptor_ptr->type);
On Fri, Jun 1, 2012 at 2:52 PM, Robin Gareus
wrote:
just a quick re: the line-numbers refered to git-head
https://github.com/jackaudio/jack2/
currently 007cdc37142a
It looks like it is indeed caused by using unions to check for /true/.
"if ([bool/int/..]union) -> always true"
But I'm at a loss what'd cause those issues and how to best fix it.
Maybe someone else can take it from here. It should be sufficient info
to file a bug report at https://github.com/jackaudio/jack2/issues
best,
robin
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
It might have to do with Arch's compiler[-flags] and how jack2 uses
unions .. or scoping: JackGlobals vs Engine-Parameters.. although I
don't have an explanation.. all seems good.
Compiler flags (for 32bit) are, (from unaltered /etc/makepkg.conf):
CXXFLAGS="-march=i686 -mtune=generic -O2 -pipe -fstack-protector
--param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2"
A hunch: it could be caused by using
'server_ptr->verbose.b' (a union)
as boolean. The sever only checks "if (server_ptr->verbose.b)". The
union itself comprises other uninitialized values that could make it
evaluate to true (though it shouldn't, but maybe some compiler
optimization casts it to (int) instead of (bool) )
I know this is the '-users' list (I'm ccing jack-devel), but could
someone who experiences the problem try to track it down?
Basically just add a few printf()'s. Start at: common/JackControlAPI.cpp
- line 926 - before the call to "new JackServer(..)" add
printf("DEBUG verbose:
%s\n",(server_ptr->verbose.b)?"on":"off");
recompile, launch jackd. If it prints "verbose: on", sth is wrong with
parameter initialization in main() or with using unions. If it's "off"
the problem sits deeper:
DEBUG verbose: on
add a line just after common/JackServer.cpp line
66
printf("DEBUG verbose2:
%s\n",(JackGlobals::fVerbose)?"on":"off");
...
above, your line number didn't match exactly, so we seem to have
different versions (1.9.7 here). Thus, I wasn't exactly sure where to
add the prinf() and did the following:
...
JackServerGlobals::fUserCount = 1; // One user
printf("DEBUG verbose2:
%s\n",(JackGlobals::fVerbose)?"on":"off");
JackGlobals::fVerbose = verbose;
printf("DEBUG verbose3:
%s\n",(JackGlobals::fVerbose)?"on":"off");
}
which prints:
DEBUG verbose2: off
DEBUG verbose3: on
A crude test for the union() hunch would be to
change
common/JackControlAPI.h line 53:
replace
"union jackctl_parameter_value"
with
"struct jackctl_parameter_value"
and compile with '-fpermissive' like this:
CXXFLAGS="-fpermissive" ./waf configure
./waf
Again, mismatching line numbers. I assume you meant the line:
union jackctl_parameter_value verbose;
Changing that to struct fixes both issues I reported,
the verbose output and exit on last client close.
So we seem to be getting somewhere. Nice.
thanks Robin,
d 
23 Jun
23 Jun
10:58 p.m.
New subject: [Jack-Devel] jack2 turned verbose
I have this issue to on i686. It is only present in jack2 1.9.8-2 and
disappears when I downgrade to 1.9.8-1. Here are the changes packaging
changes between those two:
https://projects.archlinux.org/svntogit/community.git/commit/trunk?h=packag…
Jackd remains verbose however when I manually move
40-hpet-permissions.rules to its old location.
11:50 p.m.
New subject: [Jack-Devel] jack2 turned verbose
Brendan's patch doesn't seem to help either.
24 Jun
24 Jun
3:08 a.m.
New subject: [Jack-Devel] jack2 turned verbose
On Sat, Jun 23, 2012 at 11:50 PM, Kaspar Bumke wrote:
Brendan's patch doesn't seem to help either.
For the time being, until the devs of jack2/gcc (whoever
might be the "culprit") sort it out, my user-solution is:
compiling jack2 (using the [community] package sources)
with -O0 instead of -O2.
For doing so, I just temporarely changed the CXXFLAGS
line in /etc/makepkg.conf.
best,
-d
1 Jun
1 Jun
4:30 p.m.
New subject: [Jack-Devel] jack2 turned verbose
On Fri, Jun 1, 2012 at 3:48 PM, David Adler wrote:
On Fri, Jun 1, 2012 at 2:52 PM, Robin Gareus wrote:
>
DEBUG verbose: on
Oops, I read caressly and did a change to .cpp, not the header file.
So what I did before (which somehow fixed the issues/suppressed
symptoms), was changing
"union" to "struct" in line 75 in JackControlAPI.cpp
Reverted that and did the change Robin suggested, the result is the
same, issues disappeared.
best,
d
add a line just after common/JackServer.cpp line
66
printf("DEBUG verbose2:
%s\n",(JackGlobals::fVerbose)?"on":"off");
...
above, your line number didn't match exactly, so we seem to have
different versions (1.9.7 here). Thus, I wasn't exactly sure where to
add the prinf() and did the following:
...
JackServerGlobals::fUserCount = 1; // One user
printf("DEBUG verbose2:
%s\n",(JackGlobals::fVerbose)?"on":"off");
JackGlobals::fVerbose = verbose;
printf("DEBUG verbose3:
%s\n",(JackGlobals::fVerbose)?"on":"off");
}
which prints:
DEBUG verbose2: off
DEBUG verbose3: on
A crude test for the union() hunch would be to
change
common/JackControlAPI.h line 53:
replace
"union jackctl_parameter_value"
with
"struct jackctl_parameter_value"
and compile with '-fpermissive' like this:
CXXFLAGS="-fpermissive" ./waf configure
./waf
Again, mismatching line numbers. I assume you meant the line:
union jackctl_parameter_value verbose;
Changing that to struct fixes both issues I reported,
the verbose output and exit on last client close.
3 Jun
3 Jun
10:52 p.m.
New subject: [Jack-Devel] jack2 turned verbose
On 06/01/2012 03:48 PM, David Adler wrote:
On Fri, Jun 1, 2012 at 2:52 PM, Robin Gareus wrote:
I've come a cross a jackdbus error which seems related. Basically
jackbus receives a SIGSEGV via the dbus-daemon on account of a bool
value not being 1 or 0.
The crude workaround below does nothing to explain the issue. Using a
struct in this instance is also not possible:
diff -Nurp jack-1.9.8.orig/dbus/jackdbus.c jack-1.9.8/dbus/jackdbus.c
--- jack-1.9.8.orig/dbus/jackdbus.c 2011-12-19 12:54:24.000000000 +0100
+++ jack-1.9.8/dbus/jackdbus.c 2012-06-03 22:06:16.148799580 +0200
@@ -418,6 +418,7 @@ jack_dbus_message_append_variant(
}
/* Append the supplied value. */
+ if (type == DBUS_TYPE_BOOLEAN) *arg = (message_arg_t) ((int*)arg>0);
if (!dbus_message_iter_append_basic (&sub_iter, type, (const void
*) arg))
{
dbus_message_iter_close_container (iter, &sub_iter);
Where arg is a pointer to (dbus/jackdbus.h)
typedef union
{
unsigned char byte;
dbus_bool_t boolean;
dbus_int16_t int16;
dbus_uint16_t uint16;
dbus_int32_t int32;
dbus_uint32_t uint32;
dbus_int64_t int64;
dbus_uint64_t uint64;
double doubl;
const char *string;
} message_arg_t;
It might have to do with Arch's compiler[-flags] and how jack2 uses
unions .. or scoping: JackGlobals vs Engine-Parameters.. although I
don't have an explanation.. all seems good.
Compiler flags (for 32bit) are, (from unaltered /etc/makepkg.conf):
CXXFLAGS="-march=i686 -mtune=generic -O2 -pipe -fstack-protector
--param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2"
A hunch: it could be caused by using
'server_ptr->verbose.b' (a union)
as boolean. The sever only checks "if (server_ptr->verbose.b)". The
union itself comprises other uninitialized values that could make it
evaluate to true (though it shouldn't, but maybe some compiler
optimization casts it to (int) instead of (bool) )
I know this is the '-users' list (I'm ccing jack-devel), but could
someone who experiences the problem try to track it down?
Basically just add a few printf()'s. Start at: common/JackControlAPI.cpp
- line 926 - before the call to "new JackServer(..)" add
printf("DEBUG verbose:
%s\n",(server_ptr->verbose.b)?"on":"off");
recompile, launch jackd. If it prints "verbose: on", sth is wrong with
parameter initialization in main() or with using unions. If it's "off"
the problem sits deeper:
DEBUG verbose: on
add a line just after common/JackServer.cpp line
66
printf("DEBUG verbose2:
%s\n",(JackGlobals::fVerbose)?"on":"off");
...
above, your line number didn't match exactly, so we seem to have
different versions (1.9.7 here). Thus, I wasn't exactly sure where to
add the prinf() and did the following:
...
JackServerGlobals::fUserCount = 1; // One user
printf("DEBUG verbose2:
%s\n",(JackGlobals::fVerbose)?"on":"off");
JackGlobals::fVerbose = verbose;
printf("DEBUG verbose3:
%s\n",(JackGlobals::fVerbose)?"on":"off");
}
which prints:
DEBUG verbose2: off
DEBUG verbose3: on
A crude test for the union() hunch would be to
change
common/JackControlAPI.h line 53:
replace
"union jackctl_parameter_value"
with
"struct jackctl_parameter_value"
and compile with '-fpermissive' like this:
CXXFLAGS="-fpermissive" ./waf configure
./waf
Again, mismatching line numbers. I assume you meant the line:
union jackctl_parameter_value verbose;
Changing that to struct fixes both issues I reported,
the verbose output and exit on last client close.
So we seem to be getting somewhere. Nice.
thanks Robin,
d
4 Jun
4 Jun
12:14 a.m.
New subject: [Jack-Devel] jack2 turned verbose
On 06/03/2012 10:52 PM, Brendan Jones wrote:
On 06/01/2012 03:48 PM, David Adler wrote:
In fact this is not a work around at all, it just prevents crashing. The
value is still being cast incorrectly.
On Fri, Jun 1, 2012 at 2:52 PM, Robin Gareus
wrote:
I've come a cross a jackdbus error which seems related. Basically
jackbus receives a SIGSEGV via the dbus-daemon on account of a bool
value not being 1 or 0.
The crude workaround below does nothing to explain the issue. Using a
struct in this instance is also not possible:
diff -Nurp jack-1.9.8.orig/dbus/jackdbus.c jack-1.9.8/dbus/jackdbus.c
--- jack-1.9.8.orig/dbus/jackdbus.c 2011-12-19 12:54:24.000000000 +0100
+++ jack-1.9.8/dbus/jackdbus.c 2012-06-03 22:06:16.148799580 +0200
@@ -418,6 +418,7 @@ jack_dbus_message_append_variant(
}
/* Append the supplied value. */
+ if (type == DBUS_TYPE_BOOLEAN) *arg = (message_arg_t) ((int*)arg>0);
if (!dbus_message_iter_append_basic (&sub_iter, type, (const void *) arg))
{
dbus_message_iter_close_container (iter, &sub_iter);
Where arg is a pointer to (dbus/jackdbus.h)
typedef union
{
unsigned char byte;
dbus_bool_t boolean;
dbus_int16_t int16;
dbus_uint16_t uint16;
dbus_int32_t int32;
dbus_uint32_t uint32;
dbus_int64_t int64;
dbus_uint64_t uint64;
double doubl;
const char *string;
} message_arg_t;
It might have to do with Arch's compiler[-flags] and how jack2 uses
unions .. or scoping: JackGlobals vs Engine-Parameters.. although I
don't have an explanation.. all seems good.
Compiler flags (for 32bit) are, (from unaltered /etc/makepkg.conf):
CXXFLAGS="-march=i686 -mtune=generic -O2 -pipe -fstack-protector
--param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2"
A hunch: it could be caused by using
'server_ptr->verbose.b' (a union)
as boolean. The sever only checks "if (server_ptr->verbose.b)". The
union itself comprises other uninitialized values that could make it
evaluate to true (though it shouldn't, but maybe some compiler
optimization casts it to (int) instead of (bool) )
I know this is the '-users' list (I'm ccing jack-devel), but could
someone who experiences the problem try to track it down?
Basically just add a few printf()'s. Start at: common/JackControlAPI.cpp
- line 926 - before the call to "new JackServer(..)" add
printf("DEBUG verbose:
%s\n",(server_ptr->verbose.b)?"on":"off");
recompile, launch jackd. If it prints "verbose: on", sth is wrong with
parameter initialization in main() or with using unions. If it's "off"
the problem sits deeper:
DEBUG verbose: on
add a line just after common/JackServer.cpp line
66
printf("DEBUG verbose2:
%s\n",(JackGlobals::fVerbose)?"on":"off");
...
above, your line number didn't match exactly, so we seem to have
different versions (1.9.7 here). Thus, I wasn't exactly sure where to
add the prinf() and did the following:
...
JackServerGlobals::fUserCount = 1; // One user
printf("DEBUG verbose2:
%s\n",(JackGlobals::fVerbose)?"on":"off");
JackGlobals::fVerbose = verbose;
printf("DEBUG verbose3:
%s\n",(JackGlobals::fVerbose)?"on":"off");
}
which prints:
DEBUG verbose2: off
DEBUG verbose3: on
A crude test for the union() hunch would be to
change
common/JackControlAPI.h line 53:
replace
"union jackctl_parameter_value"
with
"struct jackctl_parameter_value"
and compile with '-fpermissive' like this:
CXXFLAGS="-fpermissive" ./waf configure
./waf
Again, mismatching line numbers. I assume you meant the line:
union jackctl_parameter_value verbose;
Changing that to struct fixes both issues I reported,
the verbose output and exit on last client close.
So we seem to be getting somewhere. Nice.
thanks Robin,
d
12:55 a.m.
New subject: [Jack-Devel] jack2 turned verbose
On 06/03/2012 10:52 PM, Brendan Jones wrote:
On 06/01/2012 03:48 PM, David Adler wrote:
Compiling with -O0 also solves this error, so this could be a regression
in GCC.
On Fri, Jun 1, 2012 at 2:52 PM, Robin Gareus
wrote:
I've come a cross a jackdbus error which seems related. Basically
jackbus receives a SIGSEGV via the dbus-daemon on account of a bool
value not being 1 or 0.
It might have to do with Arch's compiler[-flags] and how jack2 uses
unions .. or scoping: JackGlobals vs Engine-Parameters.. although I
don't have an explanation.. all seems good.
Compiler flags (for 32bit) are, (from unaltered /etc/makepkg.conf):
CXXFLAGS="-march=i686 -mtune=generic -O2 -pipe -fstack-protector
--param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2"
A hunch: it could be caused by using
'server_ptr->verbose.b' (a union)
as boolean. The sever only checks "if (server_ptr->verbose.b)". The
union itself comprises other uninitialized values that could make it
evaluate to true (though it shouldn't, but maybe some compiler
optimization casts it to (int) instead of (bool) )
I know this is the '-users' list (I'm ccing jack-devel), but could
someone who experiences the problem try to track it down?
Basically just add a few printf()'s. Start at: common/JackControlAPI.cpp
- line 926 - before the call to "new JackServer(..)" add
printf("DEBUG verbose:
%s\n",(server_ptr->verbose.b)?"on":"off");
recompile, launch jackd. If it prints "verbose: on", sth is wrong with
parameter initialization in main() or with using unions. If it's "off"
the problem sits deeper:
DEBUG verbose: on
add a line just after common/JackServer.cpp line
66
printf("DEBUG verbose2:
%s\n",(JackGlobals::fVerbose)?"on":"off");
...
above, your line number didn't match exactly, so we seem to have
different versions (1.9.7 here). Thus, I wasn't exactly sure where to
add the prinf() and did the following:
...
JackServerGlobals::fUserCount = 1; // One user
printf("DEBUG verbose2:
%s\n",(JackGlobals::fVerbose)?"on":"off");
JackGlobals::fVerbose = verbose;
printf("DEBUG verbose3:
%s\n",(JackGlobals::fVerbose)?"on":"off");
}
which prints:
DEBUG verbose2: off
DEBUG verbose3: on
A crude test for the union() hunch would be to
change
common/JackControlAPI.h line 53:
replace
"union jackctl_parameter_value"
with
"struct jackctl_parameter_value"
and compile with '-fpermissive' like this:
CXXFLAGS="-fpermissive" ./waf configure
./waf
Again, mismatching line numbers. I assume you meant the line:
union jackctl_parameter_value verbose;
Changing that to struct fixes both issues I reported,
the verbose output and exit on last client close.
So we seem to be getting somewhere. Nice.
thanks Robin,
d
4322
days inactive
4348
days old
linux-audio-user@lists.linuxaudio.org
24 comments
9 participants
participants (9)
-
Brendan Jones -
david -
David Adler -
Jeremy Jongepier -
Kaspar Bumke -
mark hadman -
Ricardus Vincente -
rncbc -
Robin Gareus