I am familiar with that technique, but you only catch the to-be-debugged
fish instance while it's already sitting in its main loop, I wanted to
trace all the startup activity as well.
I ended up using a different workaround:
in one terminal:
> sh -c 'echo $$; sleep 15; exec fish'
in the other teminal:
> gdb -p <pid output above>
On 28 December 2012 02:44, ridiculous_fish <corydo...@ridiculousfish.com>wrote:
> Hi Jan,
>
> I'm not sure how to do that in one terminal, but it's straightforward with
> two.
>
> I do this in the shell targeted for debugging:
>
> > echo %self
> 26414
>
> And in another window:
>
> > gdb attach 26414
>
> In case you were't familiar with that technique, hope that helps!
>
> _fish
>
> On Dec 27, 2012, at 8:48 AM, Jan Kanis <jan.c...@jankanis.nl> wrote:
>
> Hi everyone
>
> Does anyone know how to run a shell like fish under gdb and separate gdb's
> and fish's outputs to two different terminals? I tried following
> this<http://dirac.org/linux/gdb/07-Debugging_Ncurses_Programs.php>howto for
> debugging ncurses programs, but it fails because gdb can't set
> the second terminal as fish's controlling terminal.
>
> Using ubuntu 12.04.
>
> Jan
>
>
>
>
------------------------------------------------------------------------------
Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and
much more. Get web development skills now with LearnDevNow -
350+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122812
_______________________________________________
Fish-users mailing list
Fish-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fish-users
