[lldb-dev] [Bug 39166] New: Better error messages when ptrace() fails on linux

[via lldb-dev]

https://bugs.llvm.org/show_bug.cgi?id=39166

Bug ID: 39166
   Summary: Better error messages when ptrace() fails on linux
   Product: lldb
   Version: 7.0
  Hardware: PC
OS: All
Status: NEW
  Severity: enhancement
  Priority: P
 Component: All Bugs
  Assignee: lldb-dev@lists.llvm.org
  Reporter: dav...@freebsd.org
CC: llvm-b...@lists.llvm.org

I was debugging a Linux lldb bug (on Linux).
I run linux in a VM using parallels, and for some reason lldb wasn't able to
attach to the inferior. The error message was:

"could not attach".

After a bit of scratching my head, I tried to run under gdb and I got the
following:

"Could not attach to process. If your kid matches the kid of the target
process, check the setting of /proc/sys/kerne/yama/ptrace_scope, or try again
as the root user. For more details, see /etc/sysctl.d/10-ptrace.conf.
ptrace: operation not permitted"

Which is much more informative. We might consider emitting better diagnostics
in this case (and similar ones). This is also a good beginner bug for somebody
who wants to get their feet wet and learn lldb.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] Proposal for bi-endian code debugging support for lldb.

[Chirag Patel via lldb-dev]

Hello,

Kindly correct me if I am wrong.

Now llvm has the interface to set endianity on base_types, I am looking into 
the support for lldb to debug bi-endian code (with attribute DW_AT_endianity).
Currently I am planning to record the endianity/byte-order in CompilerType 
object with context and type(inclue/lldb/Symbol/ConpilerType.h) and pass it 
along to the parent(struct/union) and while reading/wrinting data using 
data-extractor setting the byte order on that.
Any suggestions are welcomed.

Regards,

Chirag Patel| Software Engineer
RAINCODE Mainframe to .NET
Tel : +91 080 41159811 | Mob : +91 90493 36744
www.raincodelabs.com

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] Proposal for bi-endian code debugging support for lldb.

[Chirag Patel via lldb-dev]

For the moment I am planning to add it for clang typesystem.


Chirag Patel| Software Engineer
RAINCODE Mainframe to .NET
Tel : +91 080 41159811 | Mob : +91 90493 36744
www.raincodelabs.com

From: lldb-dev  On Behalf Of Chirag Patel via 
lldb-dev
Sent: 04 October 2018 11:15
To: lldb-dev@lists.llvm.org
Subject: [lldb-dev] Proposal for bi-endian code debugging support for lldb.

Hello,

Kindly correct me if I am wrong.

Now llvm has the interface to set endianity on base_types, I am looking into 
the support for lldb to debug bi-endian code (with attribute DW_AT_endianity).
Currently I am planning to record the endianity/byte-order in CompilerType 
object with context and type(inclue/lldb/Symbol/ConpilerType.h) and pass it 
along to the parent(struct/union) and while reading/wrinting data using 
data-extractor setting the byte order on that.
Any suggestions are welcomed.

Regards,

Chirag Patel| Software Engineer
RAINCODE Mainframe to .NET
Tel : +91 080 41159811 | Mob : +91 90493 36744
www.raincodelabs.com

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev