[lldb-dev] [Bug 47952] New: SIGCHLD prevents from entering breakpoint

2020-10-23 Thread via lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=47952

Bug ID: 47952
   Summary: SIGCHLD prevents from entering breakpoint
   Product: lldb
   Version: 11.0
  Hardware: PC
OS: Linux
Status: NEW
  Severity: normal
  Priority: P
 Component: All Bugs
  Assignee: lldb-dev@lists.llvm.org
  Reporter: artemhevorh...@gmail.com
CC: jdevliegh...@apple.com, llvm-b...@lists.llvm.org

- Running Ubuntu 18.04.
- Binaries for reproduction:
  - Download Swift 5.3 toolchain:
https://swift.org/builds/swift-5.3-release/ubuntu1804/swift-5.3-RELEASE/swift-5.3-RELEASE-ubuntu18.04.tar.gz
  - Download llvm toolchain v.11. 
- Commands:
  - `lldb $swiftc`, `swiftc` is path to Swift compiler.
  - Inside LLDB run:
- `breakpoint set --name Lexer` - should see this:
  - `Breakpoint 1: 8 locations.`
- `run main.swift`, where `main.swift` is a file with the following
contents:
  - `func fibbonaci(n: Int) { print("hello") }`
AT THIS POINT, I EXPECT LLDB TO STOP AT BREAKPOINT, 
INSTEAD, IT MISSES THE BREAKPOINT AND FINISHES EXECUTION OF THE PROGRAM,
REPORTING THIS ALONG THE WAY (3 TIMES):
  - `Process` X `stopped and restarted: thread 1 received signal: SIGCHLD`

Have checked this SO thread, configured the signal handler for SIGCHLD in this
way :
- `pro hand -p true -s false SIGCHLD`
With this configuration, the behaviour of lldb is completely the same as
described above.

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


[lldb-dev] [Bug 47952] SIGCHLD prevents from entering breakpoint

2020-10-23 Thread via lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=47952

Artyom Gevorgyan  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|NEW |RESOLVED

--- Comment #2 from Artyom Gevorgyan  ---
My initial problem is solved with what is described here
https://stackoverflow.com/questions/25076625/lldb-not-stopping-on-my-breakpoint.

Turns out this behaviour is expected because of internal `fork` system calls in
the software.

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


Re: [lldb-dev] [cfe-dev] Release Manager Transition

2020-10-23 Thread Richard Smith via lldb-dev
Thank you so much for all you've done as release manager, Hans. You've been
doing a truly excellent job, and you've really made a difference.

And thank you Tom for agreeing to take on this considerable but essential
task! :)

On Wed, 21 Oct 2020 at 05:13, Hans Wennborg via cfe-dev <
cfe-...@lists.llvm.org> wrote:

> After almost six years and twelve major releases (3.6 through 11), I
> have decided to step down as release manager.
>
> While I have enjoyed the process a lot, especially working with so
> many people in the community, it has taken a lot of time which I now
> want to use for other work.
>
> Tom Stellard, who already does the stable (a.k.a. "dot") releases,
> says he'd be willing to manage also the major releases, so I hereby
> nominate him to take over.
>
> Thanks,
> Hans
> ___
> cfe-dev mailing list
> cfe-...@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev