Jack Howarth wrote:
> On Fri, Oct 03, 2008 at 08:29:40PM -0500, Peter O'Gorman wrote:
>> Jack Howarth wrote:
>>> On Tue, Aug 05, 2008 at 11:31:13AM -0500, Peter O'Gorman wrote:
Jack Howarth wrote:
> Does anyone know why gdb appears to be unable to find the debug
> information
On Fri, Oct 03, 2008 at 08:29:40PM -0500, Peter O'Gorman wrote:
> Jack Howarth wrote:
> > On Tue, Aug 05, 2008 at 11:31:13AM -0500, Peter O'Gorman wrote:
> >> Jack Howarth wrote:
> >>> Does anyone know why gdb appears to be unable to find the debug
> >>> information
> >>> for libstdc++ in gcc
Jack Howarth wrote:
> On Tue, Aug 05, 2008 at 11:31:13AM -0500, Peter O'Gorman wrote:
>> Jack Howarth wrote:
>>> Does anyone know why gdb appears to be unable to find the debug
>>> information
>>> for libstdc++ in gcc 4.3 and gcc trunk on darwin9? This has been reported
>>> before
>>> as...
>
On Tue, Aug 05, 2008 at 11:31:13AM -0500, Peter O'Gorman wrote:
> Jack Howarth wrote:
> > Does anyone know why gdb appears to be unable to find the debug
> > information
> > for libstdc++ in gcc 4.3 and gcc trunk on darwin9? This has been reported
> > before
> > as...
> >
> > https://trac.ma
Peter,
You are going to fix this on gcc trunk in any case, right?
Jack
On Wed, Aug 06, 2008 at 11:17:03AM -0500, Peter O'Gorman wrote:
> Jack Howarth wrote:
> > Peter,
> > Thanks. If gcc's libtool is missing this dsymutil workaround, it would
> > be nice if this could be f
Jack Howarth wrote:
> Peter,
> Thanks. If gcc's libtool is missing this dsymutil workaround, it would
> be nice if this could be fixed for both gcc trunk and 4.3.2.
> Jack
I went and looked for the patches that added dsymutil to libtool, looks
like I took the opport
Peter,
Thanks. If gcc's libtool is missing this dsymutil workaround, it would
be nice if this could be fixed for both gcc trunk and 4.3.2.
Jack
On Tue, Aug 05, 2008 at 11:31:13AM -0500, Peter O'Gorman wrote:
> Jack Howarth wrote:
> > Does anyone know why gdb app
Jack Howarth wrote:
> Does anyone know why gdb appears to be unable to find the debug
> information
> for libstdc++ in gcc 4.3 and gcc trunk on darwin9? This has been reported
> before
> as...
>
> https://trac.macports.org/ticket/16102
>
> Under current gcc trunk, using Apple's current Xcod