[lldb-dev] Changes to 2021 GSoC program
Dear All, TL;DR: It is expected for the projects to be shorter, but more spread over the summer. Google recently announced major changes into their program for the next year. Here is the excerpt: 1. Smaller project size - all students participating in the 2021 program will be working on a 175 hour project (instead of a 350 hr project). This change will also result in a few other changes including the student stipend being cut in half. 2. Shortened coding period - the coding period will be 10 weeks with a lot more flexibility for the mentor and student to decide together how they want to spread the work out over the summer. 3. 2 evaluations (instead of 3) - There will be an evaluation after 5 weeks and the final evaluation will take place after the 10th week. The students are NO longer required to complete their first evaluation, so if a student doesn’t complete the first evaluation they will not automatically be removed from the program. They are still required to complete the final evaluation. 4. Students are no longer strongly encouraged to focus only on GSoC over their summer. Hence 2x shorter projects. And please start thinking about possible topics and scope GSoC 2021 projects :) Thanks! -- With best regards, Anton Korobeynikov Department of Statistical Modelling, Saint Petersburg State University ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 48021] New: lldb - nicer command to search for Bytes
https://bugs.llvm.org/show_bug.cgi?id=48021
Bug ID: 48021
Summary: lldb - nicer command to search for Bytes
Product: lldb
Version: unspecified
Hardware: PC
OS: MacOS X
Status: NEW
Severity: enhancement
Priority: P
Component: All Bugs
Assignee: lldb-dev@lists.llvm.org
Reporter: rustymagnet3...@gmail.com
CC: jdevliegh...@apple.com, llvm-b...@lists.llvm.org
lldb-1200.0.32.1
/*** sample code **/
// Baboon
// 0x42, 0x61, 0x62, 0x6f, 0x6f, 0x6e
const int animalByteArray[7] = { 66, 97, 98, 111, 111, 110 };
void foo_func (const void *ptr) {
printf ("\n[*]Pointer: %p.\n", ptr);/* breakpoint here */
}
int main (void) {
const int *ptr = animalByteArray;
puts ("[*]Can you change the animal?\n");
for (; *ptr != '\0'; ++ptr)
printf ("%c", *ptr);
foo_func (ptr);
return 0;
}
/***/
// Once breakpoint fires, get start and end positions for Memory Search
(lldb) section
[0x01-0x014000] 0x004000 objc_play`__TEXT
// Memory find for "B", max matches of three, from start to end address
(lldb) mem find -s "B" -c 3 -- 0x01 0x014000
WORKS
(lldb) mem find -s "B " -c 3 -- 0x01 0x014000
WORKS
But I try something more intuative:
(lldb) mem find -s "Ba" -c 3 -- 0x01 0x014000
FAILS
(lldb) mem find -s "Baboon" -c 3 -- 0x01 0x014000
FAILS
(lldb) mem find -e "\42\61" -c 10 -- 0x01 0x014000
FAILS
(lldb) mem find -e "\x42\x61" -c 10 -- 0x01 0x014000
FAILS
If I try the same with radare2 tools:
▶ rabin2 -qz objc_play
0x13f60 28 6 Baboon
Ultimately, I am trying to figure out how to write the byte buffer I pass the
lldb-python SBProcess.ReadMemory API.
--
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 48029] New: Rust function of sufficient length prevents breakpoints from working
https://bugs.llvm.org/show_bug.cgi?id=48029
Bug ID: 48029
Summary: Rust function of sufficient length prevents
breakpoints from working
Product: lldb
Version: 11.0
Hardware: Macintosh
OS: MacOS X
Status: NEW
Severity: enhancement
Priority: P
Component: All Bugs
Assignee: lldb-dev@lists.llvm.org
Reporter: d...@fritch.mn
CC: jdevliegh...@apple.com, llvm-b...@lists.llvm.org
Following up on an issue originally reported to the VsCode plug-in CodeLLDB:
https://github.com/vadimcn/vscode-lldb/issues/369
Both the author and I reached the conclusion this comes back to LLDB.
Discovered upon porting an existing (long, ~5k LOC) C function into Rust. With
this code in place, breakpoints are not resolved:
```
break list
Current breakpoints:
1: file = 'src/main.rs', line = 4, exact_match = 0, locations = 0 (pending)
2: file = 'main.rs', line = 5, exact_match = 0, locations = 0 (pending)
3: file = 'src/tests.rs', line = 13, exact_match = 0, locations = 0 (pending)
4: Exception breakpoint (catch: on throw: on) using: names =
{'__cxa_begin_catch', '__cxa_throw', '__cxa_rethrow'}, modules(2) =
libc++abi.dylib, libSystem.B.dylib
5: name = 'rust_panic', locations = 1, resolved = 1, hit count = 0
5.1: where = spice21`rust_panic + 20 at panicking.rs:626:9, address =
0x0001000acb04, resolved, hit count = 0
```
This is despite debug info being present:
```
dsymutil -s target/debug/spice21 | grep N_OSO
[ 920] 000269e1 66 (N_OSO) 03 0001
'target/debug/deps/spice21.1qcu4jwi3fjtxyk9.rcgu.o'
[ 933] 00026a80 66 (N_OSO) 03 0001
'target/debug/deps/spice21.2ql4572xdsy6ks1i.rcgu.o'
[ 946] 00026c09 66 (N_OSO) 03 0001
'target/debug/deps/spice21.2xq4mz9sgc2ysmfp.rcgu.o'
[ 955] 00026d3a 66 (N_OSO) 03 0001
'target/debug/deps/spice21.36d1auo9zjn0ja0b.rcgu.o'
[ 978] 00026f7c 66 (N_OSO) 03 0001
'target/debug/deps/spice21.3nan5uievwffbtlg.rcgu.o'
[ 991] 000270b8 66 (N_OSO) 03 0001
'target/debug/deps/spice21.4tcozfs9ntfwgd8y.rcgu.o'
[ 1001] 00027208 66 (N_OSO) 03 0001
'target/debug/deps/libspice21-1f365d6b281ad2bf.rlib(spice21-1f365d6b281ad2bf.11mevay8dm2eejnt.rcgu.o)'
[ 1029] 000274f8 66 (N_OSO) 03 0001
'target/debug/deps/libspice21-1f365d6b281ad2bf.rlib(spice21-1f365d6b281ad2bf.13zfg5ipncreabid.rcgu.o)'
[ 1039] 000276bf 66 (N_OSO) 03 0001
'target/debug/deps/libspice21-1f365d6b281ad2bf.rlib(spice21-1f365d6b281ad2bf.1442y1ntqkhpbe43.rcgu.o)'
[ 1048] 0002780c 66 (N_OSO) 03 0001
'target/debug/deps/libspice21-1f365d6b281ad2bf.rlib(spice21-1f365d6b281ad2bf.14pwkb0vdbu5d5t8.rcgu.o)'
[ 1076] 00027ac8 66 (N_OSO) 03 0001
'target/debug/deps/libspice21-1f365d6b281ad2bf.rlib(spice21-1f365d6b281ad2bf.16uddp6gzdci0bwn.rcgu.o)'
# ...
# about 150 others
```
And confirming this is not an issue with the IDE plug-in, setting the same
breakpoints via LLDB command also fails:
```
break set --file src/main.rs --line 5
Breakpoint 7: no locations (pending).
WARNING: Unable to resolve breakpoint to any actual locations.
```
All of this is on MacOS, using the stable Rust compiler and LLDB 11.
First time bug-filer here, please let me know what info will help.
--
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
