Yeah I narrowed this down to those two lines earlier, but I couldn&#39;t figure out what the exact issue was.  It narrows down to setting and accessing variables in the FilterParams struct, but I think this is a symptom and not the issue.  If i had to guess it probably has something to do with the ellipsis (...) used in the parameters, because these same operations are used in a similar print function with no problem.<div>

<br></div><div>Also, if you compile with clang++ it compiles fine, so I will try and take this new finding to the llvm bug tracker (is that the correct tracker?).</div><div><br></div><div>I have attached a new patch that uses clang++ instead of g++ (llvm) on Darwin 11.</div>

<div><br></div><div><a href="https://code.ros.org/trac/ros/attachment/ticket/3626/rosconsole_osx_clang.patch">https://code.ros.org/trac/ros/attachment/ticket/3626/rosconsole_osx_clang.patch</a></div><div><br></div><div>Not a perfect solution still but I hope this helps,</div>

<div><br clear="all">~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>William Woodall<br>Graduate Software Engineering<br>Auburn University<br><a href="mailto:w@auburn.edu" target="_blank">w@auburn.edu</a><br><a href="mailto:wjwwood@gmail.com" target="_blank">wjwwood@gmail.com</a><div>

<a href="http://williamjwoodall.com" target="_blank">williamjwoodall.com</a><br>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~</div><br>
<br><br><div class="gmail_quote">On Wed, Aug 31, 2011 at 1:21 PM, Nicholas Butko <span dir="ltr">&lt;<a href="mailto:nbutko@ucsd.edu">nbutko@ucsd.edu</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

Troy, <div><br></div><div>I added a &quot;minimal&quot; patch to the trac. It shows two lines being commented. If either of them is uncommented, a compiler segfault results. </div><div><br></div><div><a href="https://code.ros.org/trac/ros/attachment/ticket/3626/rosconsole_cpp_patch_minimal.patch" target="_blank">https://code.ros.org/trac/ros/attachment/ticket/3626/rosconsole_cpp_patch_minimal.patch</a></div>


<div><br></div><div>--Nick <br><br><div class="gmail_quote"><div><div></div><div class="h5">On Wed, Aug 31, 2011 at 10:59 AM, Troy Straszheim <span dir="ltr">&lt;<a href="mailto:straszheim@willowgarage.com" target="_blank">straszheim@willowgarage.com</a>&gt;</span> wrote:<br>


</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div></div><div class="h5"><div class="gmail_quote"><div>On Wed, Aug 31, 2011 at 10:43 AM, Nicholas Butko <span dir="ltr">&lt;<a href="mailto:nbutko@ucsd.edu" target="_blank">nbutko@ucsd.edu</a>&gt;</span> wrote:<br>


</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
I just tried to install ROS (Electric) on OSX10.7 on my machine. I ran into two hurdles. Here are the fixes: </div><div><div>2: rosmake fails, with a compiler segfault in rosconsle</div><div>I was disappointed to find that this is a known bug, with a known fix, and has been known for weeks prior to release. I&#39;m sorry to see that a version of ros shipped with what is essentially a fatal issue in its core library. It seems this is a bug in Apple&#39;s llvm-gcc, and I know that OSX is not officially supported in ROS, and that there are a lot of hard issues that WG doesn&#39;t have time to support. This one takes a few minutes, and the workaround while not ideal seems harmless. A simple #ifdef __APPLE__ could have even made the workaround only for OSX platforms, leaving Ubuntu unaffected. </div>




<div>Here is the bug/fix: <a href="https://code.ros.org/trac/ros/ticket/3626" target="_blank">https://code.ros.org/trac/ros/ticket/3626</a></div><div>It works. Thanks William for the workaround. </div>
</div></blockquote></div><br><div>I saw that patch, I didn&#39;t think that silently disabling logging on OSX was a good idea.   If you binary search with comments and/or #if 0 blocks, you can probably figure out what specific lines are confusing the compiler.  I bet it involves the va_list stuff.   Then we can figure out an actual workaround.</div>



<div><br></div><div>Also, the link to the llvm bug in that ticket is broken.  Knowing what the clang folks have to say would help.</div><div><br></div><div><br></div><div><br></div><div><br></div>
<br></div></div>_______________________________________________<br>
ros-users mailing list<br>
<a href="mailto:ros-users@code.ros.org" target="_blank">ros-users@code.ros.org</a><br>
<a href="https://code.ros.org/mailman/listinfo/ros-users" target="_blank">https://code.ros.org/mailman/listinfo/ros-users</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
ros-users mailing list<br>
<a href="mailto:ros-users@code.ros.org">ros-users@code.ros.org</a><br>
<a href="https://code.ros.org/mailman/listinfo/ros-users" target="_blank">https://code.ros.org/mailman/listinfo/ros-users</a><br>
<br></blockquote></div><br></div>