https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88745
--- Comment #13 from Eric Gallager ---
(In reply to Ian Lance Taylor from comment #12)
> Fixed.
Thanks, I backported the changeset to the (old) copy of libbacktrace I keep in
my fork of gdb and it only took a few tweaks to get it to compile.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88745
Ian Lance Taylor changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88745
--- Comment #11 from CVS Commits ---
The master branch has been updated by Ian Lance Taylor :
https://gcc.gnu.org/g:dea40c941a4d443d1b748bafb8a74f02c360e810
commit r11-251-gdea40c941a4d443d1b748bafb8a74f02c360e810
Author: Ian Lance Taylor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88745
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|10.0|10.2
--- Comment #10 from Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88745
--- Comment #9 from Ian Lance Taylor ---
filetype.awk will be run on a program compiled by the target compiler, so it
should get the correct result.
I agree that the endianness shouldn't matter with regard to the code, although
of course
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88745
--- Comment #8 from Iain Sandoe ---
(In reply to Ian Lance Taylor from comment #7)
> We are using yet another object file reader because libbacktrace is designed
> to run correctly when invoked by a signal handler, so it cannot use ordinary
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88745
--- Comment #7 from Ian Lance Taylor ---
We are using yet another object file reader because libbacktrace is designed to
run correctly when invoked by a signal handler, so it cannot use ordinary
memory allocation.
libbacktrace is only used when
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88745
--- Comment #6 from Iain Sandoe ---
(In reply to Iain Sandoe from comment #5)
> (In reply to Eric Gallager from comment #4)
> > (In reply to Ian Lance Taylor from comment #3)
> > > filetype.awk is just an AWK script. See
> > >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88745
--- Comment #5 from Iain Sandoe ---
(In reply to Eric Gallager from comment #4)
> (In reply to Ian Lance Taylor from comment #3)
> > filetype.awk is just an AWK script. See
> > https://www.gnu.org/software/gawk/manual/gawk.html. A Mach-O file
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88745
--- Comment #4 from Eric Gallager ---
(In reply to Ian Lance Taylor from comment #3)
> filetype.awk is just an AWK script. See
> https://www.gnu.org/software/gawk/manual/gawk.html. A Mach-O file starts
> with 0xfeedface (32-bit Mach-O) or
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88745
Ian Lance Taylor changed:
What|Removed |Added
CC||ian at airs dot com
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88745
--- Comment #2 from Eric Gallager ---
(In reply to Eric Gallager from comment #1)
> I tried to start doing this in my fork of gdb but I didn't get very far;
> here's a brief TODO:
>
> 1. Get filetype.awk to recognize mach-o binaries
> 2. Add a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88745
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88745
Iain Sandoe changed:
What|Removed |Added
Target||*-*-darwin*
Priority|P3
On Oct 4, 2012, at 11:23 PM, Ian Lance Taylor wrote:
On Thu, Oct 4, 2012 at 1:32 PM, Jack Howarth howa...@bromo.med.uc.edu wrote:
Is libbacktrace currently functional in gcc trunk and is it expected
to function on darwin? While I could understand it not working on installed
binaries of FSF
On Fri, Oct 5, 2012 at 9:15 AM, Tristan Gingold ging...@adacore.com wrote:
On Oct 4, 2012, at 11:23 PM, Ian Lance Taylor wrote:
On Thu, Oct 4, 2012 at 1:32 PM, Jack Howarth howa...@bromo.med.uc.edu
wrote:
Is libbacktrace currently functional in gcc trunk and is it expected
to function on
On Oct 5, 2012, at 11:37 AM, Richard Guenther wrote:
On Fri, Oct 5, 2012 at 9:15 AM, Tristan Gingold ging...@adacore.com wrote:
On Oct 4, 2012, at 11:23 PM, Ian Lance Taylor wrote:
On Thu, Oct 4, 2012 at 1:32 PM, Jack Howarth howa...@bromo.med.uc.edu
wrote:
Is libbacktrace currently
On Fri, Oct 5, 2012 at 2:37 AM, Richard Guenther
richard.guent...@gmail.com wrote:
So I take it that libbacktrace doesn't work with the separate DWARF
debuginfo as shipped by all Linux distributions either?
That does not work at present. I doubt it's difficult.
Ian
Is libbacktrace currently functional in gcc trunk and is it expected
to function on darwin? While I could understand it not working on installed
binaries of FSF gcc that were stripped, I would think it should work for
make check in the build tree since all of the debug code should be present
On Thu, Oct 4, 2012 at 1:32 PM, Jack Howarth howa...@bromo.med.uc.edu wrote:
Is libbacktrace currently functional in gcc trunk and is it expected
to function on darwin? While I could understand it not working on installed
binaries of FSF gcc that were stripped, I would think it should work
20 matches
Mail list logo
