Re: GDB and MacOS 11.4/BigSur
Sam Warner via Gdb <[email protected]>
| Newsgroups | gmane.comp.gdb.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi Simon, Thanks - yes - I’ll start with that patch first. I obtain the same call stack My next two things to learn is how to get the equivalent of the symbol-server working, and then to setup a developer-environment for GDB. Any pointers would be great. Sam Thread 2 hit Breakpoint 1, 0x00000001007cbcac in internal_error(char const*, int, char const*, ...) () (gdb) backtrace #0 0x00000001007cbcac in internal_error(char const*, int, char const*, ...) () #1 0x0000000100397902 in inferior_thread() () #2 0x00000001002bdd41 in get_current_regcache() () #3 0x000000010033bc59 in darwin_solib_create_inferior_hook(int) () #4 0x000000010036555c in symbol_file_command(char const*, int) () #5 0x0000000100159047 in file_command(char const*, int) () #6 0x00000001000b4ec1 in cmd_func(cmd_list_element*, char const*, int) () #7 0x00000001003a0ce9 in execute_command(char const*, int) () #8 0x0000000100156348 in command_handler(char const*) () #9 0x000000010015661e in command_line_handler(std::__1::unique_ptr<char, gdb::xfree_deleter<char> >&&) () #10 0x0000000100155e1a in gdb_rl_callback_handler(char*) () #11 0x000000010040ec94 in rl_callback_read_char () #12 0x0000000100156d1d in gdb_rl_callback_read_char_wrapper_noexcept() () #13 0x0000000100155b1c in gdb_rl_callback_read_char_wrapper(void*) () #14 0x000000010015623f in stdin_event_handler(int, void*) () #15 0x00000001007cc257 in gdb_wait_for_event(int) () #16 0x00000001007cbe37 in gdb_do_one_event() () #17 0x00000001001fe000 in captured_command_loop() () #18 0x00000001001fd0e5 in gdb_main(captured_main_args*) () #19 0x000000010000266c in main () (gdb) > On Jun 27, 2021, at 3:27 PM, Simon Marchi <[email protected]> wrote: > > Well, for the issue you reported specifically, please see the patch I > sent here, I think it fixes it: > > https://sourceware.org/pipermail/gdb-patches/2021-June/180396.html > > But there were other bugs reported on Bugzilla for macOS, they might > affect you as well. If you stumble on one of them, you could try to > write a fix for it and send a patch to the gdb-patches list, so that it > gets reviewed and eventually merged. > Simon > > On 2021-06-27 4:32 p.m., Sam Warner wrote: >> Hi Simon, >> Yeh, I’ve queued to do the actions for the first paragraph based on your input that few are working on resolving issues for GDB/MacOS. >> >> When you mentioned " to get patches in a good state and send them to the gdb-patches >> list for review.” I thought, well, first order of business would be this (as I saw an individual had an attempt in 10.1 to fix a null-pointer). Should I first help here? > >