Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'F' displays backtrace in single line #13

Open
vibrys opened this issue Jul 22, 2024 · 1 comment
Open

'F' displays backtrace in single line #13

vibrys opened this issue Jul 22, 2024 · 1 comment
Labels
Volunteer wanted Volunteer wanted to fix if a bug or to implement if a new feature.

Comments

@vibrys
Copy link

vibrys commented Jul 22, 2024

I'm running: ubuntu.20.04 + emacs.29.4 + realgud-lldb-20230201.948 + realgud-20231113-1910 + lldb18.1.8

after 'F' is pressed in source code buffer, whole the backtrace is put to single very long line:

 * thread #1, name = 'my_app', stop reason = breakpoint 1.1
   * frame #0: 0x00007ffff45f4b43 ..........    frame #1: 0x00007ffff45f26a3 .......    frame #2: 0x00007ffff453265d ......    ......    frame #22: 0x000055555559034e

The bt command output is correct (ie multiple lines are used) when lldb is run within linux console.

edebug returns such a result from THE LINE below:

(defun realgud:send-input ()
  "Sends command buffer line either to comint or eshell"
  (interactive)
  (let ((mode (realgud:canonic-major-mode)))
    (ignore-errors
      (cond ((eq mode 'eshell)
	     (eshell-send-input))
	    ((eq mode 'comint)
	     (comint-send-input))                  ;; THE LINE
	    ))))

@rocky rocky added the Volunteer wanted Volunteer wanted to fix if a bug or to implement if a new feature. label Jul 22, 2024
@pestctrl
Copy link

I think this is fixed by #12.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Volunteer wanted Volunteer wanted to fix if a bug or to implement if a new feature.
Projects
None yet
Development

No branches or pull requests

3 participants