search for: symboliser

...AT_linkage_name ("fqux") DW_AT_name ("fqux") DW_AT_decl_file ("TODO/llvm.hs") DW_AT_decl_line (8) DW_AT_external (true) I suspect this is a problem with the DWARF information as when I try to use `llvm-symboliser` with address 0x00000000004207c8 as retrieved from the above paste, the source location is also not reported. So, can anyone give me some practical advice about how to troubleshoot this problem/validate the DWARF information that is produced? It might also be helpful is someone could point me to...

...DW_AT_name ("fqux") >> DW_AT_decl_file ("TODO/llvm.hs") >> DW_AT_decl_line (8) >> DW_AT_external (true) >> >> I suspect this is a problem with the DWARF information as when I try >> to use `llvm-symboliser` with address 0x00000000004207c8 as retrieved >> from the above paste, the source location is also not reported. >> Yes, this is the issue. Getting llvm-symboliser to understand the DWARF information generated will get you better debugging information for XRay. >> So, can anyon...

...DW_AT_decl_file ("TODO/llvm.hs") >> >> DW_AT_decl_line (8) >> >> DW_AT_external (true) >> >> >> >> I suspect this is a problem with the DWARF information as when I try >> >> to use `llvm-symboliser` with address 0x00000000004207c8 as retrieved >> >> from the above paste, the source location is also not reported. >> >> >> >> Yes, this is the issue. Getting llvm-symboliser to understand the DWARF information generated will get you better debugging information...

Hello fellow * users Hope this isn't a stupid question; I've done my research but could not find a proper answer. I have 8 different destinations which I want to match. The numbers are: ###### 00 ###### 20 ###### 30 ###### 40 ###### 15 ###### 35 ###### 12 ###### 44 Right now I've solved it by doing this: exten => _######[0234]0,1,HangUp exten => _######[13]5,1,HangUp exten

Solaris ACLs - Files Becoming Read Only --------------------------------------- Problem: -------- Since we have upgraded to Microsoft Office 2003 from Microsoft Office 2000 we have had problems with files becoming Read Only. Background: ----------- We have read-only and write groups which have access to files. We control access using both the Samba configuration file and file system ACLs.

Samba 3.0.11 + acl (ext3) ------------------------- I have to second this, but actually we are seeing the same problem with Linux ACLS (ext3) and Office 97. Further investigation showed that although the acls seem to be inherited (eg the group has write access) the do not seem to be honoured with regard to the user. Let me give an example to clarify: 2 users: y,x belogn to group: mygroup

I don't think NDEBUG is that easy. We use assert liberally[1] in templated code in headers. What about cast<>, which has assert(isa<...>...)? On ELF, you have an ODR problem, and you'll get either one or the other based on the whims of the dynamic linker. You could probably get things to the point that it sort of works, but I don't think we could support it without

Monty wrote: > On Sat, Dec 07, 2002 at 10:29:29PM +0100, ChristianHJW wrote: > > >Please allow me to announce the creation of a new open source Media > >Container Format, named 'matroska' > > > >Project page is here http://sf.net/projects/matroska ; homepage is > >http://matroska.sourceforge.net , HTML should be online soon. > > Another redundant

Monty wrote: > On Sat, Dec 07, 2002 at 10:29:29PM +0100, ChristianHJW wrote: > > >Please allow me to announce the creation of a new open source Media > >Container Format, named 'matroska' > > > >Project page is here http://sf.net/projects/matroska ; homepage is > >http://matroska.sourceforge.net , HTML should be online soon. > > Another redundant

With the recent thread on using C++11 in LLVM/clang, one of the recurring themes was a desire to make the internal headers more consumable. While I don't personally want any kind of stability guarantee for internal headers, I do think we can do more to ensure that any given snapshot of the headers is consumable from different compilers and build configurations. In practice this means

Please allow me to announce the creation of a new open source Media Container Format, named 'matroska' Project page is here http://sf.net/projects/matroska ; homepage is http://matroska.sourceforge.net , HTML should be online soon. Steve 'robux4' LHomme and myself have left the MCF project because of incompatibilities of our work with the project goals defined by the founder of

Please allow me to announce the creation of a new open source Media Container Format, named 'matroska' Project page is here http://sf.net/projects/matroska ; homepage is http://matroska.sourceforge.net , HTML should be online soon. Steve 'robux4' LHomme and myself have left the MCF project because of incompatibilities of our work with the project goals defined by the founder of