Excuse me? I, and others, have been polite and trying to help you with
minimal information. This is unacceptable behavior and I request that you
cease the unprofessional behavior immediately.
On Mon, Nov 16, 2015, 10:19 PM Vincent Torri
wrote:
> better shut up instead of saying helpless remarks,
No, it implies you were using bfd to read dwarf, nothing else.
On Mon, Nov 16, 2015, 9:22 PM Vincent Torri wrote:
> Hello
>
> On Mon, Nov 16, 2015 at 11:05 PM, Eric Christopher
> wrote:
> > You didn't specify what compiler you were using to build the debug
> sources
> > you cared about.
>
> I'v
Hello
On Mon, Nov 16, 2015 at 11:05 PM, Eric Christopher wrote:
> You didn't specify what compiler you were using to build the debug sources
> you cared about.
I've mentioned libbfd, which implicitely specifies that i'm using a
GNU toolchain.
Vincent Torri
> Keep in mind you won't be able to l
Hello
On Mon, Nov 16, 2015 at 10:58 PM, Michael Eager wrote:
> On 11/16/2015 11:21 AM, Vincent Torri wrote:
>>
>> Hello
>>
>> the configure.in files used in dwarf source code is deprecated, in
>> favor of configure.ac. And even will not be supported anymore.
>
>
> What source code are you referri
On 11/16/2015 11:26 AM, Vincent Torri wrote:
Hello
I have begun to write a valgrind-like on Windows, and I use libbfd to
get the stack trace (file, function and line of a frame).
I would like to use libdwarf for that. But I need to port libdwarf to Windows.
On the website, it is said to contac
You didn't specify what compiler you were using to build the debug sources
you cared about. Keep in mind you won't be able to look through the system
libraries for things, but you'll be able to look at what you built at least.
-eric
On Mon, Nov 16, 2015 at 12:16 PM Vincent Torri
wrote:
> afaik,
On 11/16/2015 11:21 AM, Vincent Torri wrote:
Hello
the configure.in files used in dwarf source code is deprecated, in
favor of configure.ac. And even will not be supported anymore.
What source code are you referring to?
So, i would suggest that you rename all the configure.in files to config
afaik, gnu windows toolchain stores debug informations in DWARF
format. Am I wrong ?
Vincent Torri
On Mon, Nov 16, 2015 at 8:44 PM, Eric Christopher wrote:
> As a quick note, you're aware that Windows in general doesn't use dwarf
> right?
>
> -eric
>
> On Mon, Nov 16, 2015 at 11:26 AM Vincent To
As a quick note, you're aware that Windows in general doesn't use dwarf
right?
-eric
On Mon, Nov 16, 2015 at 11:26 AM Vincent Torri
wrote:
> Hello
>
> I have begun to write a valgrind-like on Windows, and I use libbfd to
> get the stack trace (file, function and line of a frame).
>
> I would li
Hello
I have begun to write a valgrind-like on Windows, and I use libbfd to
get the stack trace (file, function and line of a frame).
I would like to use libdwarf for that. But I need to port libdwarf to Windows.
On the website, it is said to contact this mailing list before
contributing any cod
Hello
the configure.in files used in dwarf source code is deprecated, in
favor of configure.ac. And even will not be supported anymore.
So, i would suggest that you rename all the configure.in files to configure.ac
Also, why keeping the configure files in the git repository ? It
useless as it i
11 matches
Mail list logo
