Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Dec 27 2018 06:12
    Dan-Knox commented #23
  • Dec 27 2018 06:11
    Dan-Knox commented #23
  • Jul 10 2018 08:24
    zzevikram commented #23
  • Mar 28 2018 16:34
    Pierre8r edited #27
  • Mar 28 2018 16:33
    Pierre8r opened #27
  • Feb 15 2018 20:34
    GlitchedCode opened #26
  • Dec 18 2017 19:41
    gsmcmullin closed #23
  • Dec 18 2017 19:41
    gsmcmullin commented #23
  • Dec 18 2017 19:41
    gsmcmullin commented #24
  • Dec 18 2017 19:41
    gsmcmullin closed #24
  • Dec 18 2017 19:36

    gsmcmullin on master

    Fix toggling breakpoint Require Atom 1.22.1 (compare)

  • Sep 27 2017 00:29
    clwh310 opened #25
  • Sep 17 2017 16:19
    aumars commented #5
  • Sep 17 2017 15:52
    aumars opened #24
  • Sep 10 2017 03:40
    mbmcavoy commented #23
  • Sep 02 2017 09:26
    AsGreyWolf opened #23
  • May 21 2017 14:13
    rustp opened #22
  • May 12 2017 09:58
    rustp opened #21
  • May 09 2017 13:01
    sdrshnptl opened #20
  • Feb 22 2017 22:38
    gsmcmullin commented #15
Piotr Esden-Tempski
@esden
@gsmcmullin I think you are doing the right thing here. As @alexhude and I mentioned before Sublime is on the way out, because editors like Atom and Vilual Studio Code are pushing it out of the market.
but we will always be thankfull for Sublime paving the road to how a modern text editor should look like :D
Gareth McMullin
@gsmcmullin
I'll have to take your word for that
The node/npm landscape also seems to be less of a minefield than python
Piotr Esden-Tempski
@esden
I will have to take your word for that in return. :) That is good to hear.
anyways, I am sure there is no single correct answer. But I think Atom has potential. And adding gdb support to it will give it quite an interesting leg up.
Alexander Hude
@alexhude

but we will always be thankfull for Sublime paving the road to how a modern text editor should look like

couldn't say better!

Gareth McMullin
@gsmcmullin
There is some interesting work here to produce a common debugger interface for Atom: https://github.com/AtomDebugger
It's not quite usable yet, but seems to be a good way to go, so I've joined the group and going to try work on getting it usable and moving atom-gdb-debugger over.
It's a pity I didn't see this when I first started work. I'm now trying to forget CoffeeScript and move on to ES6
Piotr Esden-Tempski
@esden
@/all Hey everyone. We have launched a Kickstarter for the 1Bitsy & Black Magic Probe V2.1 hardware today. I think this will be interesting to many of you too. I will appreciate if you would help spread the word. http://esden.net/kickstarter2016/kickstarter_splash_screen.jpg https://www.kickstarter.com/projects/esden/1bitsy-and-black-magic-probe-demystifying-arm-prog
Rick Kimball
@RickKimball
Hey
Gareth McMullin
@gsmcmullin
Hi @RickKimball
Ivan Kravets
@ivankravets
Hey @gsmcmullin :)
Gareth McMullin
@gsmcmullin
Hi @ivankravets
Ivan Kravets
@ivankravets
Great work! Have you seen https://atom.io/packages/dbg ?
Gareth McMullin
@gsmcmullin
Not a lot going on here other than people saying hi
Ivan Kravets
@ivankravets
:)
This is Ivan from PlatformIO.Org :blush:
I see a lot of requests according debugging
Gareth McMullin
@gsmcmullin
No, I don't think I've seen the package you suggest.
Ivan Kravets
@ivankravets
I've just taken a look at API and it looks very cool
Gareth McMullin
@gsmcmullin
When I started work on atom-gdb-debugger, I had a look at a few, and they all looked really weak and incomplete
Ivan Kravets
@ivankravets
I understand
I did the same in June :)
Gareth McMullin
@gsmcmullin
I'll take a look. It is a better approach to standardise the frontend, and have different backends for different debuggers
What we have here is useful, but could certainly be improved a lot. It was somewhere between an experiment to see how difficult this would be, and an effort for me to learn some web tech. On both fronts it has been successful.
I joined this group, planning to take up work here https://github.com/AtomDebugger
But have just found myself too busy with real work the last few weeks to get anything done
Ivan Kravets
@ivankravets

It is a better approach to standardise the frontend, and have different backends for different debuggers

That is why I wrote it here

Cool, great work!
Gareth McMullin
@gsmcmullin
I'll take a look in more detail when I have time. It looks more complete than the AtomDebugger projects.
Ivan Kravets
@ivankravets
Yes
It has services that could be used for integration with other atom's packages
Lee Hicks
@mr337
So I saw the video on kickstarter and trying out this atom plug, has anyone solved the f9 conflict with atom build and setting a breakpoint?
also tried to unset or remap via keymap.cson with no luck
Gareth McMullin
@gsmcmullin
Atom 1.13 has landed with some breakage. I've just pushed a new patch release to get breakpoints working again
klyngen
@klyngen
Got som really good potensial here. Breakpoints and tracking variables works nicely. UI looks good. Only problem is that I can't start the debugger. OS X
Piotr Esden-Tempski
@esden
native or BMPM?
the OS X gdb needs to be signed to be able to run on native processes.
it is a total pain in the butt to do
Aftery trying to do this several times without success it eventually worked. I am pretty sure that I have done the same set of operations every time but who knows.
there are also some stack overflow threads about this and blogs. I think I saw one that was describing how to tell the OS to load a new code signing certificate at runtime. This might have been the trick to convince OSX to accept the signature.
Lukas Bergdoll
@Voultapher
Hey :D
Maybe I'm missing something, however I can't get breakpoints to be visible
Lukas Bergdoll
@Voultapher
nvm, I'm new to linux and gdb, so forgot to compile with -g
berge472
@berge472
Awesome work. For anyone trying to use this for remote debugging you can use the 'shell' command in your init commands (or .gdbinit file) to start the gdb server:
shell gnome-terminal -e "JLinkGDBServer -device nrf52832 -if swd"
target remote :2331
break main